Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Why this matters**: Different fault-tolerance philosophies—compute vs storage. **Spark**: Lineage-based recovery. Lost partition = recompute from RDD lineage (transformations). No data replication; trades storage for compute. **Hadoop**: Block replication (default 3x)....
Why this matters: Different fault-tolerance philosophies—compute vs storage. Spark: Lineage-based recovery. Lost partition = recompute from RDD lineage (transformations). No data replication; trades storage for compute. Hadoop: Block replication (default 3x). Data-centric; node failure = read from replica. Scalability trade-offs: Spark = less storage, more recompute on failure; Hadoop = more storage, fast recovery. Long lineage = slow recovery; checkpoint truncates. Cost implications: Spark = cheaper storage, recompute cost on failure; Hadoop = 3x storage cost. Best practice: Checkpoint long lineages; use reliable storage (S3) for shuffle; consider replication for hot data.
Red Flag: Not knowing Spark can recompute. Pro-Move: 'We checkpoint every 10 stages; S3 shuffle for durability—best of both.'
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.