mediummultiple choiceObjective-mapped

Exhibit

SQS queue attributes:
  VisibilityTimeout = 30 seconds
  RedrivePolicy = not configured

CloudWatch Logs:
  14:02:11 worker-a received messageId=7b2c8f4a
  14:02:43 worker-a started payment write for order 9912
  14:03:04 worker-a message visible again before delete
  14:03:11 worker-b received messageId=7b2c8f4a
  14:03:18 worker-b repeated payment write for order 9912

Application note:
  Average handler duration is 42-55 seconds during peak load

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?

Question 1mediummultiple choice
Full question →

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?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

Increase the SQS queue batch size so each worker processes more messages per request.

Larger batches do not prevent duplicates and can worsen the blast radius when a poison message appears.

B

Distractor review

Replace SQS with Amazon SNS and let each worker subscribe directly to the topic.

SNS alone does not solve duplicate processing or provide durable buffering for slow workers.

C

Best answer

Configure a dead-letter queue and make the handler idempotent by storing a durable processed-message key.

A dead-letter queue isolates messages that repeatedly fail so they stop wasting worker capacity. Idempotency ensures a message processed more than once does not create duplicate side effects, which is essential when visibility timeouts expire or retries occur. Together, these controls address both poison-message handling and at-least-once delivery behavior.

D

Distractor review

Disable retries and shorten the visibility timeout so failed messages disappear sooner.

Disabling retries increases message loss risk, and a shorter timeout makes duplicate processing more likely when handlers are slow.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

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 make the handler idempotent by storing a durable processed-message key. — The exhibit shows a classic at-least-once delivery issue: the handler takes longer than the visibility timeout, so the same message becomes visible again and is processed twice. A dead-letter queue keeps repeatedly failing messages from clogging the queue, while idempotency protects downstream systems from duplicate writes or charges. Both controls are needed for a resilient queue consumer design. Increasing batch size only changes throughput characteristics and can make failures harder to isolate. SNS does not provide the same durable buffering semantics for slow consumers and does not solve duplicate side effects by itself. Disabling retries and shortening visibility timeout would increase message loss and duplicate delivery frequency, which is the opposite of the desired resiliency outcome.

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.

Discussion

Loading comments…

Sign in to join the discussion.