mediummultiple choiceObjective-mapped

An orders service publishes payment instructions to an Amazon SQS queue. After occasional processing timeouts, the downstream consumer sometimes processes the same instruction twice, resulting in duplicate payment attempts. The team currently uses an SQS Standard queue with a visibility timeout of 2 minutes and relies on the consumer to finish before the timeout expires. What approach best improves resilience against duplicate processing?

Question 1mediummultiple choice
Full question →

An orders service publishes payment instructions to an Amazon SQS queue. After occasional processing timeouts, the downstream consumer sometimes processes the same instruction twice, resulting in duplicate payment attempts. The team currently uses an SQS Standard queue with a visibility timeout of 2 minutes and relies on the consumer to finish before the timeout expires. What approach best improves resilience against duplicate processing?

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

Decrease visibility timeout to 10 seconds so duplicates are less likely to occur.

A shorter visibility timeout increases the chance that the message becomes visible again before processing completes, which generally increases duplicate deliveries.

B

Best answer

Make the consumer idempotent using the order ID as a deduplication key, and set the visibility timeout longer than the worst-case processing time.

SQS Standard provides at-least-once delivery, so duplicates can still occur. The most resilient design is to make the payment handler idempotent so repeated deliveries do not create duplicate side effects, and to set the visibility timeout long enough to cover the worst-case processing time to reduce unnecessary re-delivery.

C

Distractor review

Use an EventBridge rule with a fixed retry policy that only retries when the payload matches exactly.

EventBridge retries do not change the fundamental delivery semantics of SQS. Duplicate processing can still occur if the same SQS message is delivered again after the visibility timeout expires.

D

Distractor review

Enable a dead-letter queue (DLQ) only, without changing the queue type or consumer logic.

A DLQ helps isolate messages that repeatedly fail, but it does not prevent duplicate deliveries from being processed successfully more than once.

Common exam trap

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Technical deep dive

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

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?

Static NAT maps one inside address to one outside address.

What is the correct answer to this question?

The correct answer is: Make the consumer idempotent using the order ID as a deduplication key, and set the visibility timeout longer than the worst-case processing time. — Because SQS Standard uses at-least-once delivery, duplicate deliveries are possible. The strongest resilience pattern is to make the consumer idempotent so repeated messages do not cause repeated payment attempts, and to set the visibility timeout based on the longest expected processing duration to reduce re-deliveries caused by slow processing. A increases the risk of redelivery by making the visibility timeout too short. C does not address SQS delivery semantics. D only helps after repeated failures; it does not prevent duplicate processing of successfully handled messages.

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.