**Athena economics**: $5/TB scanned—inefficient queries burn budget. **Inefficient patterns**: (1) Full table scans on unpartitioned data—always partition. (2) Many small files—each incurs metadata overhead; coalesce to 128MB+ Parquet. (3) SELECT *—scan only needed columns. (4) Complex joins without partition pruning—filter early. (5) Cross joins, Cartesian products. (6) UDFs on every row. (7) OLTP-style point lookups—use RDS. **Why**: Athena is for analytical scans; it's not a database....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Capco. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.