Reviewed by Aditya Kumar · Last reviewed 2026-03-25
**Why Lazy Evaluation Exists**: Catalyst cannot optimize a single `filter`; it needs the full plan (filter + join + aggregate) to push predicates, choose join order, and eliminate redundant columns. Lazy evaluation defers execution until an action—then the full plan is optimized...
This medium-level Spark/Big Data question appears frequently in data engineering interviews at companies like Comcast. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join, partition, spark) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Why Lazy Evaluation Exists: Catalyst cannot optimize a single filter; it needs the full plan (filter + join + aggregate) to push predicates, choose join order, and eliminate redundant columns. Lazy evaluation defers execution until an action—then the full plan is optimized and executed.
Transformations: Build logical plan; return DataFrame; no execution. Examples: filter, select, join, groupBy, repartition.
Actions: Trigger execution; return result to driver or write to storage. Examples: count, collect, show, write, foreach.
Scalability Trade-offs: Multiple actions on same DF = multiple full executions. Cache (df.cache()) after expensive transformations if reused. Long lineage (100+ transformations) increases scheduler overhead; use checkpoint to truncate.
Cost Implications: Unnecessary actions (e.g., show in a loop) multiply job cost. Single action at the end of a chain is cheapest.
Pro-Move: 'We checkpoint every 10 stages in long pipelines to avoid lineage explosion.' Red Flag: Calling count() multiple times on same DF without cache—each triggers full job.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.