The correct choice is to configure a dead letter topic and handle the failed message separately. This works because Cloud Pub/Sub’s ordering keys guarantee message order within a key, but a single unacknowledged message will block all subsequent messages sharing that key. By attaching a dead letter topic to the subscription, the service automatically forwards the failing message after exhausting retry attempts (default is 5), allowing the subscription to immediately resume processing the next ordered messages without interruption. On the Google Professional Data Engineer exam, this scenario tests your understanding of how to maintain strict ordering while handling poison-pill messages—a common trap is assuming you must manually acknowledge or skip the failed message, which would break ordering guarantees. Remember the memory tip: “Dead letter topics unblock the queue, keeping order true.” This ensures the failed message can be reprocessed later from the dead letter topic without affecting the sequence of subsequent transactions.
PDE Designing data processing systems Practice Question
This PDE practice question tests your understanding of designing data processing systems. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 financial services company uses Cloud Pub/Sub with ordering keys to process transactions in order. Some messages are failing processing and getting stuck. The team wants to ensure that if a message fails, it can be reprocessed later without blocking subsequent messages. What should they implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure a dead letter topic and handle the failed message separately
Option C is correct because a dead letter topic (DLT) allows failed messages to be moved aside after exhausting retry attempts, so they do not block the processing of subsequent ordered messages. In Cloud Pub/Sub, ordering keys require messages with the same key to be delivered in order; if a message fails and is not acknowledged, it blocks all later messages with the same key. By configuring a dead letter topic, the failed message is automatically forwarded to the DLT after a maximum of 5 delivery attempts (default), and the original subscription can continue processing the next messages in order. The team can then reprocess the failed message from the DLT separately, without affecting the order of other messages.
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.
✗
Create multiple subscriptions for the same topic
Why it's wrong here
Does not preserve ordering per key.
✗
Use a pull subscription with flow control settings
Why it's wrong here
Flow control prevents overwhelming subscribers but does not handle failures.
✓
Configure a dead letter topic and handle the failed message separately
Why this is correct
Dead letter topics isolate failures, allowing forwarding of messages for later reprocessing.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the acknowledgment deadline to 600 seconds
Why it's wrong here
Does not prevent blocking, just delays timeouts.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that increasing the acknowledgment deadline or adding flow control can resolve stuck messages with ordering keys, but the real solution is to use a dead letter topic to offload the failing message and unblock the ordered stream.
Detailed technical explanation
How to think about this question
Under the hood, Cloud Pub/Sub's ordering key mechanism uses a per-key sequence number; if a message with sequence N is not acknowledged, the broker will not deliver message N+1 for the same key to that subscription. The dead letter topic feature leverages a delivery attempt counter (maxDeliveryAttempts, default 5) and a dead letter policy attached to the subscription; once the attempt limit is reached, the message is published to the DLT with the original ordering key preserved, allowing the subscription to move on. A subtle behavior is that if the DLT itself is not configured with the same ordering key, messages in the DLT are not ordered, but the original subscription resumes ordering from the next message.
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: Configure a dead letter topic and handle the failed message separately — Option C is correct because a dead letter topic (DLT) allows failed messages to be moved aside after exhausting retry attempts, so they do not block the processing of subsequent ordered messages. In Cloud Pub/Sub, ordering keys require messages with the same key to be delivered in order; if a message fails and is not acknowledged, it blocks all later messages with the same key. By configuring a dead letter topic, the failed message is automatically forwarded to the DLT after a maximum of 5 delivery attempts (default), and the original subscription can continue processing the next messages in order. The team can then reprocess the failed message from the DLT separately, without affecting the order of other messages.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses Cloud Pub/Sub with pull subscriptions to process orders. The application requires at-least-once delivery and the ability to process orders in order per customer_id. Which THREE features should they configure? (Choose three.)
hard
✓ A.Configure a dead letter topic
B.Use a push subscription with a HTTPS endpoint
✓ C.Enable ordering keys on the topic
✓ D.Enable message ordering on the subscription
E.Set the subscription's ackDeadline to 600 seconds
Why A: Correct answers are B, C, and E. Enabling ordering keys ensures messages with the same key are delivered in order. Setting exactly-once delivery on subscriptions provides at-least-once with deduplication; but exactly-once delivery on subscription actually reduces duplicates. However, the question says at-least-once, so exactly-once delivery would be too strong? Actually, exactly-once delivery on subscription ensures no duplicates, so it's even better. But if they need at-least-once, they could enable it and it still satisfies. Dead letter topics allow failed messages to be isolated and reprocessed later without blocking. A (ackDeadline of 600 seconds) is too long. D (using a push subscription) does not inherently improve ordering.
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.