The recommended approaches for handling late-arriving data in a Dataflow pipeline are configuring allowed lateness on the window and using side inputs to provide default values. Allowed lateness instructs the pipeline to keep the window state open for a specified duration after its watermark, so late elements are still included in the correct window aggregation rather than being dropped. Side inputs complement this by supplying fallback data when a late element arrives after the window has already been emitted, allowing the pipeline to process it gracefully without discarding it. On the Google Professional Data Engineer exam, this topic tests your understanding of streaming window mechanics and the trade-off between completeness and latency; a common trap is assuming side inputs alone handle lateness without setting allowed lateness, or forgetting that side inputs are read-only snapshots. Memory tip: think of allowed lateness as the “patience” of the window, and side inputs as the “safety net” for stragglers.
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.
Which TWO approaches are recommended for handling late-arriving data in a streaming Dataflow pipeline?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use side inputs to provide default values for late data.
Option A is correct because side inputs in Apache Beam (the programming model underlying Dataflow) allow you to provide default values or supplementary data to handle late-arriving elements gracefully. When a late element arrives after the window has been emitted, a side input can supply a fallback value, ensuring the pipeline can still process the data without discarding it. This approach is recommended for handling late data in streaming pipelines where completeness is not critical.
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.
✓
Use side inputs to provide default values for late data.
Why this is correct
Side inputs can supply missing data.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use fixed windows with a duration of 1 second to minimize lateness.
Why it's wrong here
Short windows do not solve late data.
✓
Configure allowed lateness on the window to accept late data.
Why this is correct
Allowed lateness specifies how late data can arrive.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set the trigger to fire only at the end of the window.
Why it's wrong here
Does not handle late data.
✗
Use a filter transform to drop late-arriving elements.
Why it's wrong here
Dropping data is not recommended.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that simply using small windows or dropping late data is a valid handling strategy, when in fact the recommended approaches involve configuring allowed lateness and using side inputs for graceful fallback.
Detailed technical explanation
How to think about this question
Under the hood, Apache Beam's windowing and triggering model uses watermark tracking to estimate event time progress. Allowed lateness (Option C) configures how long the pipeline waits after the watermark passes the window end before discarding late data; during this period, late data can still be processed and the window's pane can be re-emitted. Side inputs (Option A) can be used in conjunction with allowed lateness to provide default values when late data arrives after the allowed lateness period has expired, offering a fallback without requiring re-processing of the entire window.
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 — 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: Use side inputs to provide default values for late data. — Option A is correct because side inputs in Apache Beam (the programming model underlying Dataflow) allow you to provide default values or supplementary data to handle late-arriving elements gracefully. When a late element arrives after the window has been emitted, a side input can supply a fallback value, ensuring the pipeline can still process the data without discarding it. This approach is recommended for handling late data in streaming pipelines where completeness is not critical.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is designing a real-time clickstream analytics pipeline using Pub/Sub and Dataflow. The pipeline must handle late-arriving data (up to 1 hour) and ensure exactly-once processing. Which Dataflow feature should be configured to handle late data correctly?
easy
✓ A.Configure the trigger with allowed lateness of 1 hour.
B.Use fixed windows with a 1-hour period and enable data discarding.
C.Use session windows with a gap duration of 1 hour.
D.Set the watermark estimate to 1 hour.
Why A: Option A is correct because Dataflow's allowed lateness feature explicitly controls how long the pipeline waits for late-arriving data before closing a window. By setting allowed lateness to 1 hour, the watermark is held back, and late data within that period is still processed with exactly-once semantics. This directly addresses the requirement for handling late data up to 1 hour while ensuring no duplicates or data loss.
Last reviewed: Jun 30, 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.
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.