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?

Set the queue’s retention period to 1 minute and rely on messages expiring naturally.

Reducing retention only controls how long failed messages remain available. It does not stop the consumer from repeatedly receiving (and failing) the invalid messages during their visibility windows, and it provides no dedicated DLQ for investigation and isolation.

Increase the visibility timeout to 7 days so failed messages cannot be retried.

A long visibility timeout only delays retries by hiding messages temporarily. It does not create a failure isolation path like a DLQ, so messages can remain invisible for days, masking issues and delaying remediation.

Publish the same message again to SNS on every failure so a different subscriber might succeed.

Re-publishing on every failure can amplify load and still produce repeated duplicates. It also does not reliably isolate the specific poison messages in a DLQ for analysis, and it complicates tracing which component failed and why.

What does this SAA-C03 question test?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Configure a dead-letter queue (DLQ) with a redrive policy and set maxReceiveCount so messages move after repeated failed receives. — When messages consistently fail validation, retries can cause the consumer to repeatedly receive and fail the same poison messages, blocking progress and creating endless churn. SQS DLQs are designed to isolate such failures. By configuring a dead-letter queue with a redrive policy and setting maxReceiveCount, SQS moves a message to the DLQ after it has been received and failed processing more than the allowed number of times. The consumer stops repeatedly retrying that invalid message, while the DLQ retains the problematic messages for investigation and for implementing the required code changes. Retention expiry does not prevent repeated receiving and failing. A long visibility timeout delays retries but does not provide an explicit isolation workflow or durable failure path. Republishing to SNS can create additional duplicates and operational noise and does not specifically implement the poison-message isolation pattern that DLQs provide.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.