easyMultiple Choice
PDE Practice Question: Operating a streaming data pipeline that uses…
You are operating a streaming data pipeline that uses Cloud Pub/Sub and Dataflow. The data source sometimes emits events that are delayed by several minutes due to network issues. Your pipeline must produce accurate aggregations (e.g., counts per minute) even for late data, but you also need to avoid waiting for a long time before emitting results. Which approach should you use?
⚠ Common exam trap
Google Cloud often tests the distinction between processing-time and event-time semantics, and the trap here is that candidates may choose processing-time windows (Option A) thinking they are simpler, not realizing they sacrifice correctness for late data.
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
✓
Use event-time processing with allowed lateness and a trigger that fires early to provide speculative results.
It uses event-time processing to handle late data via allowed lateness, combined with early triggers to emit speculative results before the window closes. This balances accuracy for delayed events with low latency for downstream consumers, which is a common requirement in streaming pipelines using Cloud Pub/Sub and Dataflow.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use processing-time windows and ignore the event timestamps entirely.
Why it's wrong here
Processing-time windows key on arrival time, so a delayed event lands in the wrong minute and corrupts the counts. It is tempting because processing-time windows emit promptly without watermark logic, and they suit pipelines where arrival order matches event order and lateness never occurs.
- ✓
Use event-time processing with allowed lateness and a trigger that fires early to provide speculative results.
Why this is correct
Event-time processing aggregates by when events actually occurred, so delayed arrivals still land in the correct minute bucket. Allowed lateness retains those windows long enough to accept stragglers, while an early trigger emits speculative results promptly, satisfying the stem's dual constraint: accurate counts without long waits.
- ✗
Use global windows and hold all data for 24 hours before processing to ensure completeness.
Why it's wrong here
Global windows with a 24-hour hold cannot emit per-minute counts promptly, and a single global window discards the minute boundaries the aggregation requires. Fixed windows with allowed lateness would be correct here; holding everything maximises completeness at the cost of the low latency the scenario demands.
- ✗
Use event-time processing and discard any data that arrives after the window ends.
Why it's wrong here
Discarding late data drops the delayed events entirely, so per-minute counts stay inaccurate whenever network delays occur. Event-time processing is the right foundation, but it needs an allowed-lateness setting plus triggers or accumulation to emit early results while still incorporating late arrivals.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PDE question from scratch — 747 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.