- A
The Bigtable instance is under-provisioned; add more nodes to increase write throughput.
Why wrong: The symptoms point to pipeline-level issues, not Bigtable capacity.
- B
Change the Pub/Sub subscription from exactly-once to at-least-once delivery to avoid redelivery overhead.
Why wrong: Disabling exactly-once would increase duplicates and could lead to incorrect session metrics.
- C
The pipeline's trigger is too frequent; increase the trigger interval to 30 seconds and set allowed lateness to 1 minute to handle out-of-order events.
A longer trigger allows more events to be processed before firing, reducing duplicates and correcting out-of-order handling.
- D
The streaming engine is disabled; enable Streaming Engine to reduce worker memory pressure.
Why wrong: Streaming Engine helps with state management but does not directly address out-of-order and duplicate issues.
Quick Answer
The answer is to increase the trigger interval to 30 seconds and set allowed lateness to 1 minute. This is correct because a trigger firing every 10 seconds on a GlobalWindow causes excessive speculative commits, forcing stateful processing to handle a high rate of out-of-order and duplicate events before all data for a session arrives, which spikes processing latency and throttles Bigtable write throughput. On the Google Professional Data Engineer exam, this scenario tests your understanding of how Dataflow trigger tuning directly impacts streaming pipeline stability, often disguised as a Pub/Sub or windowing issue—a common trap is assuming exactly-once delivery eliminates duplicates, when in fact speculative triggers create them. The core concept is that increasing the trigger interval reduces state churn and write contention, while allowed lateness absorbs straggling events without reprocessing. Memory tip: think of triggers like a bus schedule—if the bus leaves too early, passengers (events) get left behind, causing chaos; give it a longer wait time and a late-passenger grace period for a smooth ride.
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing 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 gaming company uses Cloud Pub/Sub to ingest player activity events. A Dataflow streaming pipeline consumes these events, performs stateful processing to compute session metrics, and writes results to Cloud Bigtable for low-latency queries. Recently, the pipeline's processing latency increased, and the Bigtable write throughput dropped. Monitoring shows that the pipeline is experiencing a high rate of 'out-of-order' messages and 'duplicate' events. The Pub/Sub subscription is configured with exactly-once delivery. The Dataflow job uses a GlobalWindow with a trigger that fires every 10 seconds. What is the most likely cause and solution?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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
The pipeline's trigger is too frequent; increase the trigger interval to 30 seconds and set allowed lateness to 1 minute to handle out-of-order events.
Option C is correct because the high rate of out-of-order and duplicate events indicates that the pipeline's trigger is firing too frequently, causing the stateful processing to attempt to commit partial windows before all events arrive. Increasing the trigger interval to 30 seconds and setting allowed lateness to 1 minute allows the pipeline to buffer more events, reduce the number of speculative triggers, and handle late-arriving data within the lateness bound, which directly reduces processing latency and Bigtable write contention.
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.
- ✗
The Bigtable instance is under-provisioned; add more nodes to increase write throughput.
Why it's wrong here
The symptoms point to pipeline-level issues, not Bigtable capacity.
- ✗
Change the Pub/Sub subscription from exactly-once to at-least-once delivery to avoid redelivery overhead.
Why it's wrong here
Disabling exactly-once would increase duplicates and could lead to incorrect session metrics.
- ✓
The pipeline's trigger is too frequent; increase the trigger interval to 30 seconds and set allowed lateness to 1 minute to handle out-of-order events.
Why this is correct
A longer trigger allows more events to be processed before firing, reducing duplicates and correcting out-of-order handling.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
The streaming engine is disabled; enable Streaming Engine to reduce worker memory pressure.
Why it's wrong here
Streaming Engine helps with state management but does not directly address out-of-order and duplicate issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that increasing Bigtable nodes or changing Pub/Sub delivery mode will fix pipeline latency, when the real issue is the trigger configuration causing excessive speculative windowing and state churn.
Detailed technical explanation
How to think about this question
Under the hood, Dataflow's GlobalWindow with a 10-second trigger creates speculative panes that are committed early, causing state to be flushed and re-read when late data arrives, which amplifies out-of-order processing and duplicates. Allowed lateness defines how long the pipeline waits for late events before dropping them; setting it to 1 minute ensures that events arriving up to 60 seconds late are still incorporated into the correct window, reducing the need for speculative recomputation. In real-world scenarios, gaming event streams often have network jitter and client-side buffering, so a trigger interval that is too short (e.g., 10 seconds) can cause the pipeline to thrash, while a longer interval with a reasonable lateness bound smooths throughput.
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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
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.
- →
Building and operationalizing data processing systems — study guide chapter
Learn the concepts, then practise the questions
- →
Building and operationalizing 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?
Building and operationalizing data processing systems — This question tests Building and operationalizing data processing systems — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The pipeline's trigger is too frequent; increase the trigger interval to 30 seconds and set allowed lateness to 1 minute to handle out-of-order events. — Option C is correct because the high rate of out-of-order and duplicate events indicates that the pipeline's trigger is firing too frequently, causing the stateful processing to attempt to commit partial windows before all events arrive. Increasing the trigger interval to 30 seconds and setting allowed lateness to 1 minute allows the pipeline to buffer more events, reduce the number of speculative triggers, and handle late-arriving data within the lateness bound, which directly reduces processing latency and Bigtable write contention.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.