**Sqoop**: --num-mappers 4–8 (match source capacity). --fetch-size 10000. --direct for MySQL. --compress. --split-by on indexed column.
**Spark**: Repartition, broadcast joins, cache, AQE, coalesce, predicate pushdown, executor sizing.
**Shared**: Off-peak runs. Tune parallelism to source limits. Columnar formats (Parquet) for downstream.
**Why Both**: Sqoop = source-side tuning. Spark = processing-side....
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 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 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.