The answer is to configure spark.executor.memory, spark.executor.cores, and spark.executor.instances to align with the node’s total RAM. This trio directly controls the heap size per executor and the number of executors per node, allowing you to budget memory precisely and avoid out-of-memory errors without over-provisioning. On the Google Professional Data Engineer exam, this scenario tests your understanding of Spark memory management on Dataproc, where a common trap is setting executor memory too high relative to node capacity, causing container failures. The key is to calculate safe executor memory as (node memory minus OS and HDFS overhead) divided by executors per node, ensuring each executor fits within the available RAM. A helpful memory tip: remember “MEM-CORES-INSTANCES” as the three levers for tuning Spark executor memory on Dataproc.
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing data processing systems. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 company uses Cloud Dataproc for large-scale Spark jobs. They notice that some jobs are failing due to insufficient memory on the worker nodes. They want to improve memory management without over-provisioning. Which three configurations should they apply? (Choose 3)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Set spark.executor.memory to a value that fits within the node memory
Option A is correct because setting spark.executor.memory to a value that fits within the node memory ensures that each executor does not exceed the available RAM on a worker node, preventing out-of-memory (OOM) errors. This configuration directly controls the heap size allocated to each executor, and when combined with spark.executor.cores and spark.executor.instances, it allows precise memory budgeting per node. Over-provisioning is avoided by calculating the maximum safe executor memory as (node memory - OS overhead - HDFS cache) / number of executors per node.
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.
✓
Set spark.executor.memory to a value that fits within the node memory
Why this is correct
Prevents out-of-memory errors by ensuring executor memory fits worker capacity.
Related concept
Read the scenario before looking for a memorised answer.
✓
Enable Spark dynamic allocation
Why this is correct
Dynamic allocation adjusts executors based on workload, improving resource utilization.
Related concept
Read the scenario before looking for a memorised answer.
✓
Use custom machine types with high memory ratios
Why this is correct
Custom machines with more memory per CPU reduce memory pressure.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use local SSDs for temporary storage
Why it's wrong here
Local SSDs improve disk I/O, not memory management.
✗
Use preemptible worker nodes for volatile tasks
Why it's wrong here
Preemptible nodes are cost-effective but can be terminated; they don't improve memory management.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between memory management and storage optimization, so candidates mistakenly choose local SSDs (option D) thinking they help with memory, when in fact they only improve disk I/O for shuffle operations.
Detailed technical explanation
How to think about this question
Spark dynamic allocation (option B) allows the cluster to scale the number of executors up and down based on workload, which indirectly helps memory management by releasing unused executors and their associated memory back to the cluster. Custom machine types with high memory ratios (option C) let you select instances with more RAM per vCPU, such as the n2-highmem series, which is ideal for memory-intensive Spark jobs without over-provisioning CPU resources. Under the hood, Spark's memory is divided into execution and storage pools, and dynamic allocation adjusts the number of executors via the External Shuffle Service to avoid memory pressure.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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.
Designing data processing systems — This question tests Designing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Set spark.executor.memory to a value that fits within the node memory — Option A is correct because setting spark.executor.memory to a value that fits within the node memory ensures that each executor does not exceed the available RAM on a worker node, preventing out-of-memory (OOM) errors. This configuration directly controls the heap size allocated to each executor, and when combined with spark.executor.cores and spark.executor.instances, it allows precise memory budgeting per node. Over-provisioning is avoided by calculating the maximum safe executor memory as (node memory - OS overhead - HDFS cache) / number of executors per node.
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.