The answer is to examine the Dataflow monitoring UI for per-stage metrics like throughput and backlog, and to check the worker logs for error messages or stack traces. These two actions are correct because increasing system lag in a Dataflow streaming pipeline typically indicates a bottleneck where data is accumulating faster than it can be processed, and the per-stage metrics in the monitoring UI pinpoint exactly which stage is causing the backlog. Meanwhile, worker logs reveal underlying errors, such as resource contention or runtime exceptions, that may be slowing down processing. On the Google Professional Data Engineer exam, this scenario tests your ability to use Dataflow’s built-in observability tools rather than blindly scaling resources or modifying the pipeline. A common trap is to immediately adjust the number of workers or change the windowing strategy without first identifying the root cause. Remember the mnemonic “Stages show where, logs tell why” to recall that stage metrics identify the location of the lag, while logs explain the reason behind it.
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 data engineer is monitoring a Dataflow streaming pipeline and notices that the 'System Lag' metric is increasing. Which TWO actions should be taken to diagnose the issue?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check the Dataflow monitoring UI for each stage's throughput and backlog.
Option A is correct because the Dataflow monitoring UI provides per-stage metrics such as throughput and backlog, which directly indicate where data is accumulating. By examining these metrics, you can identify the specific stage causing the increasing system lag, enabling targeted troubleshooting without unnecessary pipeline changes.
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.
✓
Check the Dataflow monitoring UI for each stage's throughput and backlog.
Why this is correct
Identifies bottleneck stages.
Related concept
Read the scenario before looking for a memorised answer.
✗
Cancel the pipeline and restart with a larger initial worker count.
Why it's wrong here
Loses state; not diagnostic.
✗
Increase the maximum number of workers to handle backlog.
Why it's wrong here
Scaling may not fix the root cause like a hot key.
✓
Examine the worker logs for error messages or stack traces.
Why this is correct
Errors can cause processing stalls.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the BigQuery quota for streaming inserts.
Why it's wrong here
Sink quota may cause backpressure, but not the first diagnostic step.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between diagnostic actions and remedial actions; the trap here is that candidates confuse scaling up workers (a fix) with diagnosing the root cause of the lag.
Detailed technical explanation
How to think about this question
System Lag in Dataflow represents the time between when data is received and when it is processed, and it is calculated per worker. The monitoring UI's per-stage metrics (e.g., elements added, elements taken, and backlog) allow you to pinpoint whether the lag is due to a slow transform, a bottleneck in a GroupByKey operation, or a downstream sink issue. In real-world scenarios, increasing system lag often results from data skew or hot keys, which can be identified by examining the per-key distribution in the backlog rather than by blindly scaling workers.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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: Check the Dataflow monitoring UI for each stage's throughput and backlog. — Option A is correct because the Dataflow monitoring UI provides per-stage metrics such as throughput and backlog, which directly indicate where data is accumulating. By examining these metrics, you can identify the specific stage causing the increasing system lag, enabling targeted troubleshooting without unnecessary pipeline changes.
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.