The answer is to use Dataflow with at-least-once delivery and checkpointing, as this design directly prevents data loss during a Pub/Sub outage. Dataflow’s checkpointing mechanism periodically records the processing state, so if a Pub/Sub subscription fails, the pipeline can replay unacknowledged messages from the last checkpoint rather than starting from scratch. This ensures no events are permanently lost, even if the subscription is temporarily unavailable. On the Google Professional Data Engineer exam, this scenario tests your understanding of streaming reliability patterns—specifically how checkpointing decouples processing from transient subscription failures. A common trap is assuming Cloud Functions alone can handle outages, but they lack persistent state tracking. Remember the key distinction: Cloud Functions are stateless and event-driven, while Dataflow maintains state via checkpoints. For the exam, think “checkpoint = safety net for streaming”; if a question involves data loss during Pub/Sub outages, immediately consider Dataflow with checkpointing as the fault-tolerant solution.
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 data pipeline uses Cloud Pub/Sub to ingest events and Cloud Functions to transform and write to BigQuery. The system is experiencing data loss during Pub/Sub subscription outages. Which design change improves reliability?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Dataflow with at-least-once delivery and checkpointing
Dataflow with at-least-once delivery and checkpointing ensures that messages are not lost during Pub/Sub subscription outages because Dataflow tracks processing progress via checkpoints and can replay unacknowledged messages from the last checkpoint. This decouples the processing from the subscription's transient failures, providing fault-tolerant, exactly-once or at-least-once semantics depending on the sink.
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 Dataflow with at-least-once delivery and checkpointing
Why this is correct
Dataflow provides exactly-once semantics with checkpointing to prevent data loss.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a pull subscription with a custom app that polls frequently
Why it's wrong here
Custom polling adds complexity and still can lose messages if the puller fails.
✗
Use long ack deadlines to keep messages in the subscription
Why it's wrong here
Ack deadlines only affect redelivery; during outage, messages can still be lost if not acknowledged.
✗
Increase the timeout in Cloud Functions
Why it's wrong here
Timeout extension does not handle subscription outages.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that increasing timeouts or ack deadlines alone can prevent data loss, when in reality they only delay the inevitable loss without a replay mechanism like checkpointing or a persistent buffer.
Detailed technical explanation
How to think about this question
Dataflow's checkpointing is based on the Apache Beam runner's snapshot mechanism, which periodically saves the state of all transforms and the positions of unprocessed Pub/Sub messages. During a subscription outage, Dataflow can resume from the last checkpoint and re-read messages from the Pub/Sub snapshot or the subscription's backlog, ensuring no data is lost as long as the message retention period (default 7 days) is not exceeded. This is critical for streaming pipelines where exactly-once processing is required, as Pub/Sub itself only guarantees at-least-once delivery.
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 Dataflow with at-least-once delivery and checkpointing — Dataflow with at-least-once delivery and checkpointing ensures that messages are not lost during Pub/Sub subscription outages because Dataflow tracks processing progress via checkpoints and can replay unacknowledged messages from the last checkpoint. This decouples the processing from the subscription's transient failures, providing fault-tolerant, exactly-once or at-least-once semantics depending on the sink.
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.