Question 174 of 1,040
Design Resilient ArchitectureseasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is to configure a dead-letter queue and a redrive policy for messages that exceed the retry limit. This is correct because a dead-letter queue (DLQ) acts as a safety net for poison messages—those that fail validation repeatedly and cannot be processed successfully. By setting a redrive policy with a maximum receive count, Amazon SQS automatically moves such messages to the DLQ after the specified number of failed attempts, preventing workers from endlessly retrying the same invalid data and wasting compute resources. On the SAA-C03 exam, this scenario tests your understanding of how to decouple failure handling from main processing logic; a common trap is to assume increasing the visibility timeout or deleting the message manually is sufficient, but those approaches don’t stop infinite retries. Remember the memory tip: “DLQ = dead letter queue = dead end for poison messages”—once a message hits its retry limit, it’s redirected to the DLQ for offline analysis, not recycled back into the main queue.

SAA-C03 Design Resilient Architectures Practice Question

This SAA-C03 practice question tests your understanding of design resilient architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.

Exhibit

Worker log excerpt:
2026-04-28T09:02:11Z messageId=7f31 receiveCount=1 status=ValidationError
2026-04-28T09:03:14Z messageId=7f31 receiveCount=2 status=ValidationError
2026-04-28T09:04:17Z messageId=7f31 receiveCount=3 status=ValidationError
Queue metric: ApproximateNumberOfMessagesNotVisible keeps increasing

Based on the exhibit, some SQS messages fail validation repeatedly and continue consuming worker time. What change best prevents the bad messages from being retried forever?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "best"

    Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

Question 1easymultiple choice
Full question →

Exhibit

Worker log excerpt:
2026-04-28T09:02:11Z messageId=7f31 receiveCount=1 status=ValidationError
2026-04-28T09:03:14Z messageId=7f31 receiveCount=2 status=ValidationError
2026-04-28T09:04:17Z messageId=7f31 receiveCount=3 status=ValidationError
Queue metric: ApproximateNumberOfMessagesNotVisible keeps increasing

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 and a redrive policy for messages that exceed the retry limit.

A dead-letter queue (DLQ) with a redrive policy allows messages that have been received a maximum number of times (e.g., after the configured retry limit) to be moved to a separate queue for analysis or manual handling. This prevents the same invalid message from being repeatedly processed by workers, freeing up compute resources and avoiding infinite retry loops.

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.

  • Increase the visibility timeout so each message has more time to finish processing.

    Why it's wrong here

    A longer visibility timeout may help slow processing, but it does not stop poison messages from being retried after repeated failures.

  • Configure a dead-letter queue and a redrive policy for messages that exceed the retry limit.

    Why this is correct

    A dead-letter queue captures messages that fail repeatedly after a defined receive count. The main queue can keep processing healthy messages, while the poison messages are isolated for later inspection and remediation.

    Clue confirmation

    The clue word "best" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Replace the queue with an Amazon SNS topic so failed messages will not be retried.

    Why it's wrong here

    SNS is a publish-subscribe service, not a retry-failure mechanism for already queued messages. It does not solve repeated processing of the same bad payload.

  • Increase the number of workers so the queue drains faster during peak load.

    Why it's wrong here

    More workers can improve throughput, but they do not prevent the same malformed message from failing over and over again.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think increasing the visibility timeout or adding more workers will solve the retry problem, but neither addresses the root cause of a message that will always fail validation.

Detailed technical explanation

How to think about this question

Amazon SQS supports a redrive policy that specifies a `maxReceiveCount` (default 1, up to 1000). Once a message has been received that many times without being deleted, SQS automatically moves it to the configured DLQ. The DLQ itself must be a standard or FIFO queue, and messages in the DLQ can be retained for up to 14 days, allowing operators to inspect and reprocess or discard them. This pattern is critical for handling poison-pill messages that cannot be processed successfully.

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.

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.

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 a dead-letter queue and a redrive policy for messages that exceed the retry limit. — A dead-letter queue (DLQ) with a redrive policy allows messages that have been received a maximum number of times (e.g., after the configured retry limit) to be moved to a separate queue for analysis or manual handling. This prevents the same invalid message from being repeatedly processed by workers, freeing up compute resources and avoiding infinite retry loops.

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.

Are there clue words in this question I should notice?

Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.

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 →

How Courseiva writes practice questions · Editorial policy

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. Based on the exhibit, the team wants to stop poison messages from consuming worker capacity and also prevent duplicate side effects if the same message is delivered more than once. Which design change best meets the requirement?

medium
  • A.Increase the SQS queue batch size so each worker processes more messages per request.
  • B.Replace SQS with Amazon SNS and let each worker subscribe directly to the topic.
  • C.Configure a dead-letter queue and make the handler idempotent by storing a durable processed-message key.
  • D.Disable retries and shorten the visibility timeout so failed messages disappear sooner.

Why C: Option C is correct because a dead-letter queue isolates poison messages that repeatedly fail processing, preventing them from consuming worker capacity. Making the handler idempotent by storing a durable processed-message key (e.g., using DynamoDB or a database) ensures that even if the same message is delivered more than once, duplicate side effects are avoided. This combination directly addresses both requirements: stopping poison messages from wasting resources and preventing duplicate processing.

Keep practising

More SAA-C03 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.