hardMultiple Choice
PDE Practice Question: A company processes financial transactions using…
A company processes financial transactions using Cloud Dataflow. They need to ensure that late-arriving data is handled correctly for fraud detection. The pipeline uses event time processing. Which approach should they use to handle late data?
⚠ Common exam trap
Google Cloud often tests the misconception that sliding or session windows inherently handle late data, when in fact only explicit allowed lateness (or a similar mechanism) provides the necessary state retention and watermark adjustment for late-arriving events.
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
✓
Fixed windows with allowed lateness
Fixed windows with allowed lateness are the standard approach in Cloud Dataflow (Apache Beam) for handling late-arriving data in event-time processing. By specifying an allowed lateness duration, the pipeline retains the window state for that period, allowing late events to be correctly assigned to their original window and triggering recomputation of results. This ensures fraud detection pipelines can account for delayed transactions without missing or misordering data.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Sliding windows with early firing
Why it's wrong here
Sliding windows with early firing emit speculative results before the watermark, but early triggers do not retain state for late elements. Allowed lateness on event-time windows is what accommodates late-arriving transactions; early firing only accelerates preliminary output.
- ✗
Session windows with gap duration
Why it's wrong here
Session windows merge by activity gaps, not fixed event-time boundaries, so a late transaction may merge into the wrong session or be dropped, corrupting fraud patterns. Sessions suit user-activity grouping, not fixed-interval financial aggregation with allowed lateness.
- ✓
Fixed windows with allowed lateness
Why this is correct
Allowed lateness extends a fixed window's lifetime, so late-arriving events still trigger updated panes rather than being discarded as dropped data. This satisfies the event-time fraud-detection requirement by emitting revised results after the watermark passes.
- ✗
Global windows with triggers
Why it's wrong here
Global windows place all elements in one never-closing window, so late data cannot be separated into meaningful time-based accumulations for fraud detection. They suit unbounded aggregations where timing is irrelevant. Allowed lateness with event-time windows is required here.
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.