Quick Answer
The answer is Data freshness (seconds), as this metric directly measures the lag between when an event occurs and when it is processed by the Dataflow pipeline. This metric, exposed as system_lag in Dataflow monitoring, reflects the difference between the event time and the processing time, making it the definitive indicator of how up-to-date your streaming output is relative to the input watermark. For the Google Professional Data Engineer exam, this tests your understanding of real-time pipeline health and SLA compliance—a common trap is confusing data freshness with system latency or throughput, which measure different aspects of performance. Remember that freshness tells you if your pipeline is keeping pace with incoming events, not just how fast it processes them. A useful memory tip: think of “freshness” as the age of the data at the output—if it’s too old, your pipeline is falling behind, and you need to alert on that lag to maintain near-real-time processing guarantees.
This PDE practice question tests your understanding of building and operationalizing data processing systems. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
You are monitoring a Dataflow streaming job and need to track the freshness of data being processed. What metric should you alert on?
Output throughput (elements/sec)
Why wrong: Throughput measures processing rate, not freshness.
Error count
Why wrong: Error count indicates failures, not data freshness.
Data freshness (seconds)
Data freshness measures the latency of the last processed event, indicating pipeline delay.
CPU utilization
Why wrong: CPU utilization reflects compute load, not how recent the data is.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Data freshness (seconds)
Data freshness (seconds) is the correct metric to alert on because it directly measures the lag between when an event occurs and when it is processed by the Dataflow pipeline. This metric, exposed as the 'system_lag' in Dataflow monitoring, indicates how up-to-date the output is relative to the input watermark. Alerting on data freshness ensures that the pipeline is meeting service-level agreements (SLAs) for real-time or near-real-time processing.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Output throughput (elements/sec)
Why it's wrong here
Throughput measures processing rate, not freshness.
Error count
Why it's wrong here
Error count indicates failures, not data freshness.
Data freshness (seconds)
Why this is correct
Data freshness measures the latency of the last processed event, indicating pipeline delay.
Related concept
Read the scenario before looking for a memorised answer.
CPU utilization
Why it's wrong here
CPU utilization reflects compute load, not how recent the data is.
Common exam traps
Google Cloud often tests the distinction between throughput and latency metrics, and the trap here is that candidates confuse high throughput with low latency, not realizing that a pipeline can process many elements per second while still having stale data due to watermark delays or unprocessed late data.
Detailed technical explanation
Data freshness in Dataflow is derived from the watermark, which is the system's estimate of the event time up to which all data has been processed. The 'data_freshness' metric (also called 'system_lag') is computed as the difference between the current wall-clock time and the watermark, and it can spike due to late-arriving data, straggler sources, or insufficient worker resources. In a real-world scenario, a pipeline processing IoT sensor readings might show low throughput but acceptable freshness if the watermark advances quickly, whereas high throughput with a stalled watermark indicates a backlog that requires scaling or tuning of triggers.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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 — study guide chapter
Learn the concepts, then practise the questions
Building and operationalizing data processing systems practice questions
Targeted practice on this topic area only
All PDE questions
499 questions across all exam domains
Google Professional Data Engineer study guide
Full concept coverage aligned to exam objectives
PDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PDE questions linked to Designing data processing systems.
Practise PDE questions linked to Building and operationalizing data processing systems.
Practise PDE questions linked to Operationalizing machine learning models.
Practise PDE questions linked to Ensuring solution quality.
Practise PDE questions linked to PDE fundamentals.
Practise PDE questions linked to PDE scenario.
Practise PDE questions linked to PDE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
The correct answer is: Data freshness (seconds) — Data freshness (seconds) is the correct metric to alert on because it directly measures the lag between when an event occurs and when it is processed by the Dataflow pipeline. This metric, exposed as the 'system_lag' in Dataflow monitoring, indicates how up-to-date the output is relative to the input watermark. Alerting on data freshness ensures that the pipeline is meeting service-level agreements (SLAs) for real-time or near-real-time processing.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
Last reviewed: Jun 30, 2026
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.