Question 749 of 1,000

Dataflow System Lag Metric — Alert on Pipeline Latency

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.

Your Dataflow streaming pipeline is processing financial transactions and writing results to BigQuery. You need to monitor the pipeline for data freshness (end-to-end latency) and alert if it exceeds 5 minutes. The pipeline uses fixed windows of 1 minute. Which metrics should you use for alerting?

Quick Answer

The answer is the System Lag metric from Dataflow monitoring. This metric directly measures the difference between event time and processing time, quantifying how far behind the pipeline is in processing data—exactly what you need to alert on end-to-end latency for a streaming pipeline with fixed windows. On the Google Professional Data Engineer exam, this question tests your ability to distinguish between Dataflow’s internal latency metrics and BigQuery-specific or resource-level metrics. A common trap is confusing System Lag with Data Freshness, but Data Freshness is a BigQuery table-level metric for how current the data is in storage, not pipeline processing delay. Remember: System Lag = pipeline heartbeat; Data Freshness = table clock. For your alert on a 5-minute threshold, System Lag is the direct, pipeline-native indicator of data freshness in flight.

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

System Lag metric from Dataflow monitoring.

System Lag in Dataflow measures the maximum time that a data element waits in the pipeline before being processed, which directly reflects end-to-end latency. For a streaming pipeline with 1-minute fixed windows, System Lag indicates how far behind the pipeline is from real-time, making it the correct metric to alert on when data freshness exceeds 5 minutes.

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.

  • System Lag metric from Dataflow monitoring.

    Why this is correct

    System Lag tracks the delay between event time and processing time; if it exceeds 5 minutes, alert.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Data Freshness metric from BigQuery monitoring.

    Why it's wrong here

    Data Freshness is for BigQuery tables, not for the Dataflow pipeline latency.

  • Element Count metric from Dataflow monitoring.

    Why it's wrong here

    Element Count shows number of elements processed, not latency.

  • Worker Threads Utilization metric from Dataflow monitoring.

    Why it's wrong here

    This measures CPU utilization, not how fast data is flowing through the pipeline.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google often tests the distinction between pipeline-level latency metrics (System Lag) and sink-level freshness metrics (BigQuery Data Freshness), trapping candidates who confuse the two or assume any 'freshness' metric is appropriate for the pipeline itself.

Trap categories for this question

  • Command / output trap

    Element Count shows number of elements processed, not latency.

Detailed technical explanation

How to think about this question

System Lag is computed by the Dataflow service as the difference between the current watermark and the processing time, representing how far behind the pipeline is in real time. In a streaming pipeline with fixed windows, System Lag can spike due to straggler data or backpressure, and alerting on it at a threshold of 5 minutes ensures that windowed results are written to BigQuery within acceptable freshness bounds. A real-world scenario is a financial fraud detection pipeline where a System Lag exceeding 5 minutes could mean delayed alerts, leading to compliance violations.

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.

Related practice questions

Related PDE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PDE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PDE question test?

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: System Lag metric from Dataflow monitoring. — System Lag in Dataflow measures the maximum time that a data element waits in the pipeline before being processed, which directly reflects end-to-end latency. For a streaming pipeline with 1-minute fixed windows, System Lag indicates how far behind the pipeline is from real-time, making it the correct metric to alert on when data freshness exceeds 5 minutes.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PDE practice questions

Last reviewed: Jul 4, 2026

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.

Loading comments…

Sign in to join the discussion.

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.