- A
A FIFO queue without a redrive policy
Why wrong: FIFO ordering does not solve repeated processing failure.
- B
A dead-letter queue with an appropriate maxReceiveCount
A DLQ isolates messages that fail repeatedly so they can be investigated without disrupting normal processing.
- C
A larger message retention period only
Why wrong: Longer retention keeps messages longer but does not isolate poison messages.
- D
Short polling instead of long polling
Why wrong: Polling mode changes request efficiency, not poison message handling.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. A key principle to apply: a Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.. 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 payments API uses Amazon SQS. Poison messages are repeatedly failing and blocking useful retries. What should the architect configure? The architecture review board prefers a managed AWS-native control.
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
A dead-letter queue with an appropriate maxReceiveCount
A dead-letter queue (DLQ) with an appropriate maxReceiveCount is the correct AWS-native solution for handling poison messages. When a message is repeatedly received from an SQS queue but fails processing, it is considered a poison message. By configuring a DLQ and setting a maxReceiveCount (e.g., 3 or 5), the message is automatically moved to the DLQ after exceeding that threshold, preventing it from blocking further retries and allowing the main queue to process valid messages.
Key principle: A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A FIFO queue without a redrive policy
Why it's wrong here
FIFO ordering does not solve repeated processing failure.
- ✓
A dead-letter queue with an appropriate maxReceiveCount
Why this is correct
A DLQ isolates messages that fail repeatedly so they can be investigated without disrupting normal processing.
Related concept
A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.
- ✗
A larger message retention period only
Why it's wrong here
Longer retention keeps messages longer but does not isolate poison messages.
- ✗
Short polling instead of long polling
Why it's wrong here
Polling mode changes request efficiency, not poison message handling.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse poison message handling with ordering or polling optimizations, and incorrectly choose FIFO queues or short polling, not realizing that only a DLQ with a redrive policy isolates repeatedly failing messages.
Detailed technical explanation
How to think about this question
Under the hood, SQS uses the ReceiveCount attribute to track how many times a message has been received. When this count exceeds the maxReceiveCount set on the source queue's redrive policy, SQS automatically moves the message to the configured DLQ. This is a managed, asynchronous process that does not require custom code or Lambda triggers. In real-world scenarios, poison messages often result from transient data corruption or incompatible schema changes, and the DLQ allows operators to inspect, fix, or replay messages without impacting production throughput.
KKey Concepts to Remember
- A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.
- A redrive policy on a source queue links it to a DLQ and defines the `maxReceiveCount`.
- Messages are moved to the DLQ when their `ReceiveCount` exceeds the `maxReceiveCount`.
- DLQs prevent poison messages from continuously blocking the main queue's processing.
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
A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.
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. A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts. 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.
Review a Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design Resilient Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Resilient Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 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 SAA-C03 question test?
Design Resilient Architectures — This question tests Design Resilient Architectures — A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts..
What is the correct answer to this question?
The correct answer is: A dead-letter queue with an appropriate maxReceiveCount — A dead-letter queue (DLQ) with an appropriate maxReceiveCount is the correct AWS-native solution for handling poison messages. When a message is repeatedly received from an SQS queue but fails processing, it is considered a poison message. By configuring a DLQ and setting a maxReceiveCount (e.g., 3 or 5), the message is automatically moved to the DLQ after exceeding that threshold, preventing it from blocking further retries and allowing the main queue to process valid messages.
What should I do if I get this SAA-C03 question wrong?
Review a Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
A Dead-Letter Queue (DLQ) isolates messages that fail processing after a specified number of attempts.
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 11, 2026
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services 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 SAA-C03 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.