SAA-C03 Dead-Letter Queue (DLQ) Practice Question
A claims workflow 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.
⚠ Common exam trap
A common mix-up: candidates confuse a DLQ with simply increasing retention or changing polling behavior, not realizing that poison messages require explicit isolation via a separate queue and a maxReceiveCount threshold to stop infinite retries.
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 allows messages that repeatedly fail processing to be moved out of the source queue after a specified number of receive attempts. This prevents poison messages from blocking useful retries and is a fully managed AWS-native pattern. The architecture review board's preference for a managed solution is satisfied because SQS DLQs are a built-in feature requiring no custom code.
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 remove poison messages; without a redrive policy, repeatedly failing messages remain and block the queue, so the workflow stalls. It is tempting because FIFO guarantees ordering for claims processing, which is the right choice when strict sequence matters, but a dead-letter queue is needed here.
- ✗
Short polling instead of long polling
Why it's wrong here
Polling mode changes how quickly consumers receive messages, not how failing messages are isolated or retried, so poison messages still block the queue. It is tempting because short polling reduces cost and latency, which is the correct choice when optimising throughput rather than handling repeated delivery failures.
- ✓
A dead-letter queue with an appropriate maxReceiveCount
Why this is correct
A dead-letter queue with maxReceiveCount moves messages aside once they exceed the receive threshold, so poison messages stop blocking useful retries. This satisfies the review board's managed AWS-native constraint, since DLQs are a native SQS feature requiring no custom code or third-party tooling.
- ✗
A larger message retention period only
Why it's wrong here
Extending retention only keeps failing messages longer, so they continue to be redelivered and block useful retries. It is tempting because retention settings govern how long messages survive, which is the correct choice when messages must persist for delayed consumers, not when repeated failures must be quarantined.
Go deeper
Related to this question
About these practice questions
Courseiva writes every SAA-C03 question from scratch — 935 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.