**Lazy**: Transformations build DAG; nothing runs until action. Catalyst optimizes full plan. PySpark default.
**Eager**: Each op runs immediately. Pandas, traditional SQL. No cross-op optimization.
**Why Lazy**: Catalyst needs full plan for predicate pushdown, join reorder, constant folding. Single execution of optimized plan.
**Trade-offs**: Lazy = optimization, single execution. Eager = immediate feedback, no optimization.
**Scalability Trade-offs**: Long lineage = scheduler overhead....
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 Incedo. 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.