The answer is acknowledgment deadlines, message persistence, and subscriber retry with exponential backoff. These three features work together to guarantee at-least-once delivery while enabling exactly-once processing downstream because Cloud Pub/Sub stores every published message redundantly across multiple zones, and the subscriber must explicitly acknowledge each message within a configurable deadline; if the deadline expires or the subscriber fails, Pub/Sub redelivers the message, and the retry policy with exponential backoff prevents overwhelming the subscriber during transient failures. On the Google Professional Data Engineer exam, this question tests your understanding that at-least-once delivery is a Pub/Sub guarantee, but exactly-once processing is a downstream responsibility achieved through idempotent consumers and deduplication logic. A common trap is confusing Pub/Sub’s delivery semantics with processing semantics—remember that Pub/Sub never guarantees exactly-once delivery, only at-least-once. Memory tip: “ACK or retry, never lose a message—persist and backoff for exactly-once processing.”
PDE Practice Question: Building and operationalizing data processing systems
This PDE practice question tests your understanding of building and operationalizing data processing systems. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 THREE features of Cloud Pub/Sub guarantee at-least-once delivery and enable exactly-once processing downstream? (Choose three.)
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "least"
Why it matters: You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Subscriber-retry policy with exponential backoff.
Option A is correct because a subscriber-retry policy with exponential backoff ensures that messages that fail to be processed are retried with increasing delays, preventing transient failures from causing message loss. This mechanism, combined with Pub/Sub's persistent storage, guarantees that each message is delivered at least once, as the subscriber will keep retrying until it acknowledges the message.
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.
✓
Subscriber-retry policy with exponential backoff.
Why this is correct
Retries ensure messages are eventually delivered on failure.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✓
Exactly-once delivery source feature (enabled by default in current gcloud).
Why this is correct
This ensures that publishers cannot duplicate messages.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Message ordering by message key.
Why it's wrong here
Ordering provides FIFO, not delivery guarantees.
✗
Cloud Dataproc integration for message replay.
Why it's wrong here
Dataproc is not directly involved in Pub/Sub delivery guarantees.
✓
Acknowledgment deadlines and message persistence.
Why this is correct
Messages are stored until acknowledged; deadlines trigger redelivery.
Clue confirmation
The clue word "least" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that message ordering or replay features contribute to delivery guarantees, when in fact ordering is about sequence and replay is not a native Pub/Sub capability; the key trap is confusing 'exactly-once delivery' (which Pub/Sub does not offer) with 'exactly-once processing' (which requires subscriber-side idempotency).
Detailed technical explanation
How to think about this question
Under the hood, Pub/Sub's at-least-once delivery is enforced by the server not removing a message from storage until it receives an acknowledgment from the subscriber. The acknowledgment deadline (default 10 seconds, max 600 seconds) can be extended by the subscriber, and if the deadline expires without acknowledgment, the message is redelivered. Exactly-once processing downstream is achieved by the subscriber implementing idempotent processing (e.g., using a unique message ID or a deduplication key), not by Pub/Sub itself—Pub/Sub does not guarantee exactly-once delivery, only at-least-once.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
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 — 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: Subscriber-retry policy with exponential backoff. — Option A is correct because a subscriber-retry policy with exponential backoff ensures that messages that fail to be processed are retried with increasing delays, preventing transient failures from causing message loss. This mechanism, combined with Pub/Sub's persistent storage, guarantees that each message is delivered at least once, as the subscriber will keep retrying until it acknowledges the message.
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: "least". You want the option with minimum overhead, fewest steps, or lowest impact — not the most feature-rich or comprehensive answer.
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.