SAA-C03 Design Resilient Architectures Practice Question
A consumer application reads from an Amazon SQS queue. Some messages have an invalid format and always fail processing. They are retried repeatedly and consume consumer capacity. What is the best way to prevent these "poison pill" messages from blocking normal processing?
⚠ Common exam trap
Test-takers frequently think increasing retention or polling settings will solve the problem, but they fail to recognize that only a DLQ with a redrive policy isolates repeatedly failing messages from consuming consumer capacity.
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 a dead-letter queue (DLQ) with a redrive policy and a maxReceiveCount.
A dead-letter queue (DLQ) with a redrive policy and a maxReceiveCount allows messages that repeatedly fail processing to be moved to a separate queue after a specified number of receive attempts. This prevents poison pill messages from being retried indefinitely, freeing consumer capacity for valid messages. Amazon SQS automatically redirects messages to the DLQ once the maxReceiveCount threshold is exceeded, ensuring normal processing is not blocked.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable long polling and increase the maximum message retention to 30 days.
Why it's wrong here
Long polling affects how long the consumer waits for messages during ReceiveMessage, not how many times a failing message is retried. Increasing retention only keeps problematic messages available longer; it does not automatically isolate them.
- ✓
Configure a dead-letter queue (DLQ) with a redrive policy and a maxReceiveCount.
Why this is correct
A DLQ with a redrive policy isolates poison-pill messages. After a message fails processing and is received more than maxReceiveCount times, SQS stops returning it to the main queue and moves it to the DLQ. Normal messages continue to be processed without repeatedly consuming consumer capacity.
- ✗
Switch the queue to FIFO and disable retries in the consumer code.
Why it's wrong here
FIFO affects ordering, not the automated quarantine behavior for repeated failures. Disabling retries in code may reduce retries temporarily, but it does not provide the built-in maxReceiveCount-based routing to a DLQ that systematically isolates poison pills.
- ✗
Delete the main queue and recreate it after every failure.
Why it's wrong here
Deleting and recreating the main queue after every failure is operationally disruptive and does not provide any automation for handling poison-pill messages. SQS queues are meant to be durable and continuously available; recreating them risks losing in-flight messages, breaks any existing queue policies or consumers, and introduces significant latency and complexity. In contrast, a DLQ with a redrive policy automatically quarantines messages after a configurable number of receive attempts, allowing the main queue to keep processing healthy messages without manual intervention.
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 935-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.