**Broadcast Join**: Small table sent to all executors; each does local hash join. No shuffle of large table.
**Why Required**: Shuffle join on 100GB + 1GB = shuffle 100GB. Broadcast 1GB = each executor gets 1GB; no shuffle. 10–100x faster.
**When**: Small table < ~100MB (configurable via spark.sql.autoBroadcastJoinThreshold). Manual: `broadcast(df)`.
**Trade-offs**: Broadcast table must fit in executor memory. Oversized = OOM....
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 Nagarro. 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 Spark/Big Data 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.