- A
Sliding windows with early firing
Why wrong: Early firing may cause duplicate or incomplete results.
- B
Session windows with gap duration
Why wrong: Session windows are designed for user activity sessions, not fixed-time windows.
- C
Fixed windows with allowed lateness
Allowed lateness includes late events in the correct window.
- D
Global windows with triggers
Why wrong: Global windows accumulate all data, not suitable for time-based fraud detection.
Quick Answer
The answer is fixed windows with allowed lateness, which is the correct approach for handling late-arriving data in Cloud Dataflow when using event time processing. This works because allowed lateness instructs the pipeline to retain the window state for a specified duration after the watermark passes, ensuring that late events are still assigned to their original window and trigger a recomputation of results, such as updated fraud detection aggregates. On the Google Professional Data Engineer exam, this concept tests your understanding of how Dataflow manages out-of-order data within the Beam model, often appearing as a scenario where you must distinguish between fixed windows with allowed lateness and alternatives like global windows or triggers without state retention. A common trap is confusing allowed lateness with simply dropping late data or using processing time windows, but the key is that allowed lateness preserves window state for late-arriving data to maintain accuracy. Remember the mnemonic: "Late data? Don't truncate—just set your lateness and recalculate."
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing 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.
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?
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
Option C is correct because 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.
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.
- ✗
Sliding windows with early firing
Why it's wrong here
Early firing may cause duplicate or incomplete results.
- ✗
Session windows with gap duration
Why it's wrong here
Session windows are designed for user activity sessions, not fixed-time windows.
- ✓
Fixed windows with allowed lateness
Why this is correct
Allowed lateness includes late events in the correct window.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Global windows with triggers
Why it's wrong here
Global windows accumulate all data, not suitable for time-based fraud detection.
Common exam traps
Common exam trap: answer the scenario, not the keyword
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.
Detailed technical explanation
How to think about this question
Under the hood, Cloud Dataflow's allowed lateness mechanism works by maintaining a watermark that tracks the progress of event time; when a late event arrives (after the watermark has passed the window end), the pipeline checks if the event is within the allowed lateness period and, if so, re-triggers the window's aggregation. This is implemented via the `withAllowedLateness` method in Apache Beam, which sets a duration (e.g., 1 hour) during which the window state is preserved. In real-world fraud detection, late-arriving credit card transactions from different time zones or network delays can be correctly processed without dropping them, ensuring accurate alerting.
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.
- →
Designing data processing systems — study guide chapter
Learn the concepts, then practise the questions
- →
Designing 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
Related PDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Designing data processing systems practice questions
Practise PDE questions linked to Designing data processing systems.
Building and operationalizing data processing systems practice questions
Practise PDE questions linked to Building and operationalizing data processing systems.
Operationalizing machine learning models practice questions
Practise PDE questions linked to Operationalizing machine learning models.
Ensuring solution quality practice questions
Practise PDE questions linked to Ensuring solution quality.
PDE fundamentals practice questions
Practise PDE questions linked to PDE fundamentals.
PDE scenario practice questions
Practise PDE questions linked to PDE scenario.
PDE troubleshooting practice questions
Practise PDE questions linked to PDE troubleshooting.
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?
Designing data processing systems — This question tests Designing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Fixed windows with allowed lateness — Option C is correct because 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.
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 →
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.