The answer is to use session windows with a gap duration and configure allowed_lateness. This combination is correct because session windows dynamically group events based on a period of inactivity—the gap duration—making them ideal for aggregating user sessions that may span multiple hours, while the allowed_lateness parameter instructs the pipeline to hold the window open for late-arriving data, preventing any discard. On the Google Professional Data Engineer exam, this scenario tests your understanding of how Dataflow handles out-of-order and late data in streaming pipelines, often appearing as a trap where candidates mistakenly choose fixed or sliding windows, which cannot accommodate variable-length sessions. A common memory tip is to think of session windows as “elastic buckets” that stretch with user activity, and allowed_lateness as a “grace period” for stragglers—just remember: sessions need gaps, late data needs lateness.
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing data processing systems. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 real-time clickstream data from websites. They need to aggregate user sessions that may span multiple hours and handle events that arrive late due to network delays. The pipeline must avoid discarding late data. Which Dataflow feature should they configure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use session windows with a gap duration and allow late data with a suitable allowed_lateness
Session windows are ideal for aggregating user sessions that span multiple hours, as they group events based on a gap duration of inactivity. By configuring `allowed_lateness`, the pipeline can handle late-arriving events without discarding them, ensuring completeness. This directly addresses the requirement to avoid discarding late data while aggregating sessions.
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 fixed windows with a trigger that fires after every element
Why it's wrong here
Fixed windows with per-element trigger cause too many outputs and may still discard late data.
✓
Use session windows with a gap duration and allow late data with a suitable allowed_lateness
Why this is correct
Session windows group events within a gap, and allowed_lateness accommodates late arrivals.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use the GlobalWindow with a watermark
Why it's wrong here
GlobalWindow does not handle session gaps and may not suit the use case.
✗
Use sliding windows with no allowed lateness
Why it's wrong here
Sliding windows without allowed lateness discard late data entirely.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the distinction between window types and late-data handling; the trap here is that candidates might choose fixed or sliding windows without realizing they lack the session-gap logic needed for variable-length user sessions, or they might overlook the `allowed_lateness` parameter as the key to preserving late data.
Trap categories for this question
Command / output trap
Fixed windows with per-element trigger cause too many outputs and may still discard late data.
Detailed technical explanation
How to think about this question
Session windows in Dataflow (Apache Beam) are defined by a `gap_duration` (e.g., 30 minutes) that merges windows if events occur within that gap. The `allowed_lateness` parameter (default 0) specifies how long after the watermark the system waits for late data; setting it to a few hours (e.g., 2 hours) ensures late events are still processed. Under the hood, Dataflow uses a watermark to track event time progress, and late data is held in a state store until the allowed lateness expires, after which it is discarded.
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 healthcare organisation deploys an application with a public-facing web tier and a private database tier. The database subnet has no public IP and only accepts connections from the web tier's security group. Questions like this test whether you can design cloud network isolation using VNets/VPCs, subnets, and security group rules.
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 session windows with a gap duration and allow late data with a suitable allowed_lateness — Session windows are ideal for aggregating user sessions that span multiple hours, as they group events based on a gap duration of inactivity. By configuring `allowed_lateness`, the pipeline can handle late-arriving events without discarding them, ensuring completeness. This directly addresses the requirement to avoid discarding late data while aggregating sessions.
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 →
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.