- A
Set the consumer visibility timeout to a very large value so failing messages are hidden for hours.
Why wrong: A long visibility timeout only postpones retries. Poison messages will still reappear once the timeout expires and can still consume receive/processing capacity, potentially continuing to impact throughput.
- B
Configure an SQS redrive policy to send messages to a dead-letter queue (DLQ) after a limited number of receives (maxReceiveCount).
A DLQ redrive policy creates a deterministic stop condition for poison messages. After maxReceiveCount, the messages are moved to the DLQ instead of cycling in the main queue, preventing repeated failed deliveries from degrading capacity and availability for valid messages.
- C
Switch the SQS queue from Standard to FIFO so poison messages do not retry.
Why wrong: FIFO queues preserve ordering (and provide deduplication), but they do not eliminate retry behavior. Without a DLQ/redrive policy, poison messages can still be received and retried until the retry limit is reached by application logic or retention/processing patterns.
- D
Increase the consumer concurrency indefinitely so the system processes all messages even if some fail validation.
Why wrong: Higher concurrency may improve throughput for a time, but it does not remove poison messages from the system. The poison messages can still consume CPU/network resources repeatedly and can increase contention, costs, and instability rather than isolating the failures.
Quick Answer
The answer is to configure an SQS redrive policy that sends messages to a dead-letter queue (DLQ) after a limited number of receives, such as a maxReceiveCount of 3 to 5. This is correct because the redrive policy automatically moves poison messages—those that repeatedly fail validation and keep reappearing—to a separate DLQ after they exceed the specified receive threshold, isolating them from the main queue. This prevents the failing messages from consuming visibility timeout and processing resources, allowing valid messages to be handled without delay while the DLQ can be analyzed or reprocessed offline. On the SAA-C03 exam, this scenario tests your understanding of SQS’s built-in poison message handling versus manual approaches like increasing visibility timeout or using a separate consumer; a common trap is thinking you must delete or ignore the messages, but the resilient solution is to offload them for later investigation. Memory tip: think “three strikes and you’re out”—set maxReceiveCount to 3, and the DLQ catches the poison.
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. 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.
An event-driven order processing service consumes messages from an Amazon SQS Standard queue. After a deployment, about 1% of messages start failing validation because a required field is missing. The consumer catches the exception and returns control, so the messages are retried. However, those poison messages keep reappearing and repeatedly consuming processing time for hours, delaying handling of valid messages. What is the most resilient way to handle the poison messages while keeping the system available?
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
Configure an SQS redrive policy to send messages to a dead-letter queue (DLQ) after a limited number of receives (maxReceiveCount).
Option B is correct because configuring an SQS redrive policy with a maxReceiveCount (e.g., 3–5) automatically moves messages that repeatedly fail processing to a dead-letter queue (DLQ) after the specified number of receives. This isolates the poison messages, preventing them from consuming visibility timeout and processing resources, while allowing valid messages to be handled without delay. The DLQ can then be analyzed or reprocessed offline, maintaining system availability.
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.
- ✗
Set the consumer visibility timeout to a very large value so failing messages are hidden for hours.
Why it's wrong here
A long visibility timeout only postpones retries. Poison messages will still reappear once the timeout expires and can still consume receive/processing capacity, potentially continuing to impact throughput.
- ✓
Configure an SQS redrive policy to send messages to a dead-letter queue (DLQ) after a limited number of receives (maxReceiveCount).
Why this is correct
A DLQ redrive policy creates a deterministic stop condition for poison messages. After maxReceiveCount, the messages are moved to the DLQ instead of cycling in the main queue, preventing repeated failed deliveries from degrading capacity and availability for valid messages.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Switch the SQS queue from Standard to FIFO so poison messages do not retry.
Why it's wrong here
FIFO queues preserve ordering (and provide deduplication), but they do not eliminate retry behavior. Without a DLQ/redrive policy, poison messages can still be received and retried until the retry limit is reached by application logic or retention/processing patterns.
- ✗
Increase the consumer concurrency indefinitely so the system processes all messages even if some fail validation.
Why it's wrong here
Higher concurrency may improve throughput for a time, but it does not remove poison messages from the system. The poison messages can still consume CPU/network resources repeatedly and can increase contention, costs, and instability rather than isolating the failures.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think increasing visibility timeout or concurrency solves the problem, but they fail to recognize that only a dead-letter queue permanently isolates poison messages from the processing pipeline.
Detailed technical explanation
How to think about this question
Under the hood, SQS uses a redrive policy with a maxReceiveCount to track the number of times a message has been received (via the ReceiveCount attribute). Once the threshold is exceeded, the message is automatically moved to the configured DLQ, which can be a Standard or FIFO queue. In real-world scenarios, this pattern is critical for decoupling error handling from main processing, allowing operations teams to inspect DLQ messages (e.g., via CloudWatch alarms or Lambda triggers) and fix the root cause (e.g., schema validation bugs) without impacting live traffic.
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.
- →
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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure an SQS redrive policy to send messages to a dead-letter queue (DLQ) after a limited number of receives (maxReceiveCount). — Option B is correct because configuring an SQS redrive policy with a maxReceiveCount (e.g., 3–5) automatically moves messages that repeatedly fail processing to a dead-letter queue (DLQ) after the specified number of receives. This isolates the poison messages, preventing them from consuming visibility timeout and processing resources, while allowing valid messages to be handled without delay. The DLQ can then be analyzed or reprocessed offline, maintaining system availability.
What should I do if I get this SAA-C03 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 →
Same concept, more angles
1 more ways this is tested on SAA-C03
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 service consumes messages from an SQS queue. Recently, a new message format started failing validation in the consumer. The consumer catches the exception but cannot successfully process those messages without code changes. The team wants failed messages to be isolated for later investigation instead of being retried indefinitely. What should they configure?
medium- A.Set the queue’s retention period to 1 minute and rely on messages expiring naturally.
- ✓ B.Configure a dead-letter queue (DLQ) with a redrive policy and set maxReceiveCount so messages move after repeated failed receives.
- C.Increase the visibility timeout to 7 days so failed messages cannot be retried.
- D.Publish the same message again to SNS on every failure so a different subscriber might succeed.
Why B: A dead-letter queue (DLQ) with a redrive policy is the correct solution because it allows messages that repeatedly fail processing to be moved to a separate queue after exceeding the maxReceiveCount. This isolates problematic messages for later investigation without blocking the main queue or causing infinite retries. The consumer catches the exception, so the message is not deleted and is returned to the queue for redelivery; the DLQ ensures that after a configurable number of attempts, the message is redirected instead of being retried indefinitely.
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.