- A
Use side inputs to join late data with the main stream.
Why wrong: Side inputs are not designed for late event handling; they are for supplementary data.
- B
Use streaming inserts into BigQuery and ignore late data.
Why wrong: Ignoring late data compromises data quality; proper handling is expected for reliable pipelines.
- C
Configure triggers with allowed lateness and accumulation of late firings.
This is the standard pattern for handling late data in Dataflow: set allowed lateness and use triggers to emit on late arrival.
- D
Increase the window duration to cover late data.
Why wrong: Larger windows increase latency and do not guarantee all late data is captured; they also change aggregation semantics.
PDE Ensuring solution quality Practice Question
This PDE practice question tests your understanding of ensuring solution quality. 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 data pipeline using Dataflow processes streaming data. Late-arriving events are currently being dropped. How should the team modify the pipeline to ensure late data is processed correctly?
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
Configure triggers with allowed lateness and accumulation of late firings.
Option C is correct because Dataflow's triggers allow you to configure allowed lateness and accumulation of late firings, which ensures that late-arriving events are still processed within the correct window. By setting `withAllowedLateness` and specifying accumulation mode (e.g., `ACCUMULATING`), the pipeline will emit additional panes for late data and merge them with the existing window results, preventing data loss.
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 join late data with the main stream.
Why it's wrong here
Side inputs are not designed for late event handling; they are for supplementary data.
- ✗
Use streaming inserts into BigQuery and ignore late data.
Why it's wrong here
Ignoring late data compromises data quality; proper handling is expected for reliable pipelines.
- ✓
Configure triggers with allowed lateness and accumulation of late firings.
Why this is correct
This is the standard pattern for handling late data in Dataflow: set allowed lateness and use triggers to emit on late arrival.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Increase the window duration to cover late data.
Why it's wrong here
Larger windows increase latency and do not guarantee all late data is captured; they also change aggregation semantics.
Common exam traps
Common exam trap: answer the scenario, not the keyword
A common misconception is that simply increasing the window duration or using side inputs can handle late data in Dataflow, when in fact only trigger-based mechanisms with allowed lateness and accumulation provide the precise control needed for streaming late-arriving events.
Detailed technical explanation
How to think about this question
Under the hood, Dataflow's `withAllowedLateness` sets a time duration after the watermark passes the end of a window during which late data is still accepted. When combined with accumulation triggers (e.g., `AfterWatermark.pastEndOfWindow().withLateFirings()`), the pipeline emits speculative and late panes, and the final result includes all data within the allowed lateness period. A subtle behavior is that if accumulation is set to `DISCARDING`, late firings will overwrite previous panes, which can lead to data loss if not configured correctly for the use case.
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.
- →
Ensuring solution quality — study guide chapter
Learn the concepts, then practise the questions
- →
Ensuring solution quality practice questions
Targeted practice on this topic area only
- →
All PDE questions
1,000 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.
Ingesting and Processing the Data practice questions
Practise PDE questions linked to Ingesting and Processing the Data.
Storing the Data practice questions
Practise PDE questions linked to Storing the Data.
Preparing and Using Data for Analysis practice questions
Practise PDE questions linked to Preparing and Using Data for Analysis.
Maintaining and Automating Data Workloads practice questions
Practise PDE questions linked to Maintaining and Automating Data Workloads.
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?
Ensuring solution quality — This question tests Ensuring solution quality — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure triggers with allowed lateness and accumulation of late firings. — Option C is correct because Dataflow's triggers allow you to configure allowed lateness and accumulation of late firings, which ensures that late-arriving events are still processed within the correct window. By setting `withAllowedLateness` and specifying accumulation mode (e.g., `ACCUMULATING`), the pipeline will emit additional panes for late data and merge them with the existing window results, preventing data loss.
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 →
Keep practising
More PDE practice questions
- A company wants to process large CSV files stored in Cloud Storage and load them into BigQuery. The files are generated…
- A company runs a Dataflow streaming pipeline that reads from Cloud Pub/Sub and writes to BigQuery. The pipeline uses a s…
- A company uses Cloud Dataproc for ephemeral clusters to run batch jobs. They want to ensure job reliability and data qua…
- Your company uses Vertex AI Pipelines to automate model retraining. The pipeline has three steps: data extraction from B…
- A company wants to use BigQuery to query data stored in Parquet files in Cloud Storage without loading the data into Big…
- A company has deployed a machine learning model to AI Platform Prediction. The model uses a custom container with a Tens…
Last reviewed: Jul 4, 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.