mediummulti selectObjective-mapped

A payment worker consumes messages from an Amazon SQS queue. Sometimes the worker finishes the payment creation, but a timeout prevents message deletion and the same payment request is delivered again. Which two design changes best reduce the risk of duplicate charges and keep bad messages from looping forever? Select two.

Question 1mediummulti select
Full question →

A payment worker consumes messages from an Amazon SQS queue. Sometimes the worker finishes the payment creation, but a timeout prevents message deletion and the same payment request is delivered again. Which two design changes best reduce the risk of duplicate charges and keep bad messages from looping forever? Select two.

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

Best answer

Make the payment operation idempotent by storing a unique request identifier before charging.

Idempotency ensures the same business request cannot create multiple charges if SQS redelivers the message.

B

Distractor review

Reduce the visibility timeout so retries happen sooner after each timeout.

A shorter visibility timeout usually increases duplicate processing pressure and does not prevent repeated charges.

C

Distractor review

Move the queue to Amazon SNS so each message is delivered only once.

SNS is a publish-subscribe service, not a durable work queue with exactly-once processing guarantees.

D

Distractor review

Increase the message retention period so failed payments stay available longer.

Longer retention preserves messages, but it does not stop duplicates or isolate poison messages.

E

Best answer

Configure a dead-letter queue with a redrive policy for messages that exceed the max receive count.

A dead-letter queue stops poison messages from consuming worker capacity forever and preserves them for later inspection.

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: Make the payment operation idempotent by storing a unique request identifier before charging. — Idempotent payment handling is essential because SQS can redeliver messages when a worker times out after already completing the business action. Recording a unique request identifier lets the system recognize a duplicate and avoid charging twice. A dead-letter queue with redrive limits removes repeatedly failing messages from the main queue so they do not loop endlessly and block healthy work. Reducing the visibility timeout makes redelivery happen faster, which can increase duplicate processing if the first attempt was actually successful. SNS is not a replacement for a work queue and does not provide queue-style retry control. Longer retention only keeps messages around longer; it does not solve duplicates or poison-message handling.

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.