**When**: One join side fits in memory across executors (typically < ~100MB, configurable via `spark.sql.autoBroadcastJoinThreshold`). **How**: Use `broadcast(df)` hint or rely on Spark auto-broadcast. Driver sends the small table to all executors; join runs locally without shuffle of the large table. **Why**: Shuffle of a large fact table is expensive (network, disk, serialization); broadcasting the dimension avoids it....
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 Altimetrik, Infosys. 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 2 companies. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.