Databricks-Spark-Assoc Spark Architecture and Components Practice Question
Which property of RDDs (Resilient Distributed Datasets) is primarily responsible for Spark's fault tolerance during cluster execution?
⚠ Common exam trap
Candidates often confuse RDD Lineage with Data Replication. They mistakenly believe Spark handles fault tolerance by copying data to other nodes, rather than recomputing lost partitions from the recorded lineage.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The RDD Lineage graph.
Lineage (the dependency graph) is the core mechanism of RDD fault tolerance. Because RDDs are immutable and record their transformation history, Spark can reconstruct lost partitions by recomputing them from their parent RDDs. This is superior to traditional replication models because it avoids the high cost of copying data over the network, allowing Spark to maintain resilience while maximizing performance and minimizing storage overhead across the distributed cluster infrastructure.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Data replication across multiple nodes.
Why it's wrong here
While HDFS provides replication, Spark's native fault tolerance for RDDs relies on lineage, not replication. Reliance on replication would impose significant network and storage overhead. Lineage allows for efficient, recomputable data recovery, which is the defining feature of Spark's architecture compared to older, replication-based Big Data systems.
- ✓
The RDD Lineage graph.
Why this is correct
Lineage tracks the sequence of transformations applied to the data. If a node fails, Spark uses this graph to recompute only the lost partitions, ensuring the job completes successfully without needing a complete restart. This design is what makes Spark highly resilient in large, distributed compute environments.
- ✗
The Spark Driver's checkpointing of all intermediate tasks.
Why it's wrong here
The Driver does not checkpoint all intermediate tasks, as doing so would create a massive performance bottleneck. Only explicitly requested checkpoints (via checkpoint() calls) are stored, whereas lineage-based recovery is the default and standard method for handling typical worker node failures during the job execution lifecycle.
- ✗
The use of a centralized data warehouse.
Why it's wrong here
Spark does not require a centralized warehouse for fault tolerance. Its resilience is built into the DAG and lineage model, allowing it to function efficiently on transient data or object storage. Relying on an external warehouse would defeat the purpose of distributed processing and introduce unnecessary latency.
About these practice questions
One of 295 original Databricks-Spark-Assoc practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Databricks exam blueprint
This Databricks-Spark-Assoc practice question is part of Courseiva's free Databricks certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the Databricks-Spark-Assoc exam.