The answer is to configure a Dead Letter Queue (DLQ) with a redrive policy, as this is the specific SQS feature designed to isolate problematic messages after repeated processing failures. A DLQ acts as a secondary queue where messages are automatically redirected once they have been received from the source queue more times than the threshold defined in the redrive policy’s maxReceiveCount setting—in this scenario, three attempts. This mechanism allows the SysOps administrator to quarantine failed messages for manual review without disrupting the main processing flow. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this concept frequently appears in scenario-based questions testing your understanding of message lifecycle management and error handling patterns. A common trap is confusing a DLQ with a delay queue or a FIFO queue’s deduplication; remember that the DLQ’s sole purpose is to catch messages that exceed their receive count. Memory tip: think “three strikes and you’re out”—the maxReceiveCount is the strike limit, and the DLQ is the penalty box.
SOA-C02 Reliability and Business Continuity Practice Question
This SOA-C02 practice question tests your understanding of reliability and business continuity. 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 company processes orders using an Amazon SQS standard queue. The order processing application occasionally fails to process a message. The SysOps administrator wants to ensure that any message that fails to be successfully processed after three attempts is automatically moved to a separate queue for manual review. Which SQS feature should be configured?
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
A Dead Letter Queue (DLQ) with a configured redrive policy is the correct SQS feature to automatically move messages that have failed processing after a specified number of attempts (in this case, three) to a separate queue for manual review. The redrive policy defines the source queue, the DLQ, and the maximum receive count (maxReceiveCount) threshold. When a message is received from the source queue more times than the maxReceiveCount, SQS automatically redirects it to the DLQ, isolating problematic messages without manual intervention.
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.
✓
Configure a Dead Letter Queue (DLQ) with a redrive policy
Why this is correct
DLQs automatically move messages to a separate queue after the specified number of receive attempts.
Related concept
Read the scenario before looking for a memorised answer.
✗
Increase the visibility timeout of the queue
Why it's wrong here
Visibility timeout impacts how long a message is hidden but does not move failed messages to another queue.
✗
Convert the queue to a FIFO queue
Why it's wrong here
FIFO queues provide ordering and deduplication but do not automatically handle failed messages.
✗
Enable redrive allow policy on the queue
Why it's wrong here
Redrive allow policy controls which source queues can use the DLQ, but does not move messages itself.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse increasing the visibility timeout (which only delays reprocessing) with the automatic isolation provided by a Dead Letter Queue, or think that converting to FIFO or enabling a redrive allow policy alone solves the problem, when the core requirement is a DLQ with a configured redrive policy that specifies the maxReceiveCount.
Detailed technical explanation
How to think about this question
Under the hood, the redrive policy is a JSON object attached to the source queue that specifies the deadLetterTargetArn (the ARN of the DLQ) and maxReceiveCount (an integer, e.g., 3). When a message's receive count exceeds maxReceiveCount, SQS uses the redrive policy to atomically move the message to the DLQ, decrementing the source queue's approximateNumberOfMessagesNotVisible metric. A subtle behavior is that the DLQ must be of the same type (standard or FIFO) as the source queue, and the source queue must have a redrive permission policy that allows the source queue to send messages to the DLQ.
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.
Reliability and Business Continuity — This question tests Reliability and Business Continuity — 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 Queue (DLQ) with a redrive policy — A Dead Letter Queue (DLQ) with a configured redrive policy is the correct SQS feature to automatically move messages that have failed processing after a specified number of attempts (in this case, three) to a separate queue for manual review. The redrive policy defines the source queue, the DLQ, and the maximum receive count (maxReceiveCount) threshold. When a message is received from the source queue more times than the maxReceiveCount, SQS automatically redirects it to the DLQ, isolating problematic messages without manual intervention.
What should I do if I get this SOA-C02 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 →
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 SOA-C02 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 SOA-C02 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.