Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why it matters**: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams. Narrow transformations process each partition independently—no shuffle (map, filter, mapPartitions). Wide transformations require...
This hard-level Spark/Big Data question appears frequently in data engineering interviews at companies like Morgan Stanley. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join, optimization, partition) will help you answer variations of this question confidently.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Why it matters: At scale, design choices directly impact reliability, latency, and cost. Wrong decisions compound across jobs and teams.
Narrow transformations process each partition independently—no shuffle (map, filter, mapPartitions). Wide transformations require shuffling data across partitions (groupBy, join, distinct, repartition). Use narrow when possible for speed. Use wide when aggregation or joins are required. For joins: broadcast small tables (under 100MB) to avoid shuffle; for aggregations, consider reduceByKey (partial aggregation) over groupByKey. Best practice: df.broadcast(small_df).join(large_df) for small dimension joins; repartition before wide ops if partition count is suboptimal.
Scalability trade-offs: Partition/parallelism limits; single points of failure; horizontal vs vertical scaling. Cost implications: Sizing, spot vs reserved, optimization ROI.
Red Flag: GroupByKey when ReduceByKey works. Pro-Move: 'reduceByKey has combiner; 10x less shuffle.'
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.