easyMultiple Choice
PDE Practice Question: Running a Cloud Dataflow streaming pipeline that…
A company is running a Cloud Dataflow streaming pipeline that aggregates events in 1-minute windows. They notice that the watermark is lagging significantly behind real-time. What is the most likely cause?
⚠ Common exam trap
Google Cloud often tests the misconception that watermark lag is caused by configuration settings like window duration or allowed lateness, rather than by data-level issues like hot keys that create processing bottlenecks.
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
✓
A hot key is causing data skew.
A hot key causes data skew, which means a disproportionate amount of data is assigned to a single key. In Cloud Dataflow, this leads to a single worker processing the bulk of the events, creating a processing bottleneck. The watermark, which tracks the progress of event-time processing, cannot advance until all data for a given window is processed, so the skewed key delays watermark progression significantly behind real-time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A hot key is causing data skew.
Why this is correct
A hot key concentrates processing on one key, so a single worker stalls while others idle, delaying window closure and holding the watermark back. Data skew therefore explains the lagging watermark in the 1-minute windowed pipeline.
- ✗
The window duration is too short.
Why it's wrong here
Window duration sets how events are grouped, not how the watermark advances; a one-minute window still emits once the watermark passes it. It is tempting because short windows surface late data quickly, but the watermark lags due to unprocessed input, not window size.
- ✗
The pipeline was recently updated.
Why it's wrong here
A pipeline update does not itself hold back the watermark; the watermark tracks the minimum unprocessed event time, so lag stems from data arriving late or from upstream backlog. Updates are tempting because they can briefly pause processing, but they are not the mechanism that advances or delays watermarks.
- ✗
The allowed lateness is set too high.
Why it's wrong here
Allowed lateness governs how long late data is retained after the watermark passes a window; it does not delay the watermark itself. It is tempting because both concern late-arriving events, but the watermark is driven by the minimum unprocessed timestamp, not by the lateness setting.
Go deeper
Related to this question
About these practice questions
This PDE question is part of Courseiva's 747-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.