**Choose Broadcast**: When one table is small (<~100MB). Avoids shuffle of large table. 10–100x faster.
**Choose Shuffle**: When both tables large. Broadcast would OOM.
**Memory Risk**: Broadcast table sent to every executor. Must fit in executor memory. Oversized = driver or executor OOM.
**Mitigation**: Monitor broadcast size. spark.sql.autoBroadcastJoinThreshold (default 10MB). Manual broadcast() when appropriate....
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 Microsoft. 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.