The answer is a cluster with a standard master node and 10 preemptible worker nodes (n1-standard-4) for cost-effective Spark batch processing on Dataproc. This configuration leverages preemptible VMs, which offer roughly an 80% discount, to handle the distributed transformations and aggregations of large CSV files, while Spark’s built-in fault tolerance through RDD lineage ensures that any lost worker tasks are automatically recomputed, making preemptible instances ideal for ephemeral batch workloads. On the Google Professional Data Engineer exam, this scenario tests your understanding of balancing cost and reliability in Dataproc—a common trap is choosing all-standard nodes for “safety,” which wastes budget, or all-preemptible nodes, which risks master instability. Remember the memory tip: “Master stays, workers play—preemptible pays.”
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing data processing systems. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A data engineer needs to process large CSV files (hundreds of GB) stored in Cloud Storage using Spark on a Dataproc cluster. The job performs a series of transformations and aggregations. Which configuration is most cost-effective and operationally efficient?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a cluster with a standard master node and 10 preemptible worker nodes (n1-standard-4).
Option B is correct because preemptible workers are significantly cheaper (about 80% discount) and ideal for batch processing of large CSV files where fault tolerance is built into Spark via RDD lineage. Using standard nodes for the master ensures cluster stability, while preemptible workers handle the distributed transformations and aggregations cost-effectively. This configuration balances cost and operational efficiency for ephemeral, fault-tolerant workloads.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use a cluster with 10 high-memory (n1-highmem-8) VMs as workers to improve shuffle performance.
Why it's wrong here
High-memory machines are more expensive; standard machines are usually sufficient.
✓
Use a cluster with a standard master node and 10 preemptible worker nodes (n1-standard-4).
Why this is correct
Preemptible workers are cost-effective and suitable for fault-tolerant jobs like Spark.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a single-node cluster with a high-memory machine type.
Why it's wrong here
A single-node cluster cannot efficiently process hundreds of GB due to memory and CPU constraints.
✗
Use a cluster with 10 standard (n1-standard-4) VMs as master and worker nodes, all non-preemptible.
Why it's wrong here
Non-preemptible VMs are more expensive; using preemptible workers reduces cost.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that preemptible VMs are unreliable for all workloads, but in Spark batch processing with fault tolerance, they are both cost-effective and operationally efficient, unlike stateful or latency-sensitive applications.
Detailed technical explanation
How to think about this question
Preemptible VMs in Google Cloud are short-lived (max 24 hours) and can be terminated at any time, but Spark's lineage-based fault tolerance allows recomputation of lost partitions from shuffle files or source data. For large CSV files, reading from Cloud Storage (using the GCS connector) is resilient to node preemption because data is not stored locally. A common real-world scenario is using preemptible workers for ETL pipelines that run nightly, where cost savings of 60-80% are achieved while maintaining SLA through checkpointing or speculative execution.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a cluster with a standard master node and 10 preemptible worker nodes (n1-standard-4). — Option B is correct because preemptible workers are significantly cheaper (about 80% discount) and ideal for batch processing of large CSV files where fault tolerance is built into Spark via RDD lineage. Using standard nodes for the master ensures cluster stability, while preemptible workers handle the distributed transformations and aggregations cost-effectively. This configuration balances cost and operational efficiency for ephemeral, fault-tolerant workloads.
What should I do if I get this PDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PDE practice question is part of Courseiva's free Google Cloud 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 PDE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.