The correct answer is to make the consumer idempotent by storing a processed payment key and rejecting repeat charges. This approach directly addresses the core problem of duplicate payments by ensuring that even if a worker times out after submitting a charge but before deleting the message, retrying the same message will not result in a second payment. The technical concept here is idempotency: by persisting a unique transaction identifier (like a payment key) and checking it before processing, the system can safely retry without side effects. On the SAA-C03 exam, this scenario tests your understanding of how to design fault-tolerant, distributed systems on AWS—often using services like SQS, Lambda, or DynamoDB to store idempotency tokens. A common trap is assuming that simply deleting the message faster or using a FIFO queue alone prevents duplicates, but idempotency is the only solution that preserves retry behavior while guaranteeing exactly-once processing. Memory tip: think “IDEM” for “Idempotency Defeats Extra Money”—store the key, reject the repeat.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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
Amazon SQS worker log:
2026-04-27T14:02:11Z Received messageId=82f3a9 paymentId=78341 receiveCount=1
2026-04-27T14:02:57Z Charged card successfully for paymentId=78341
2026-04-27T14:03:05Z Timeout occurred before DeleteMessage
2026-04-27T14:03:12Z Received messageId=82f3a9 paymentId=78341 receiveCount=2
2026-04-27T14:03:43Z Duplicate charge blocked manually
Queue configuration:
VisibilityTimeout=30 seconds
RedrivePolicy=not configured
Based on the exhibit, duplicate payment charges occasionally occur when the worker times out after the charge is submitted but before the message is deleted. What change best prevents duplicate charges while keeping retry behavior?
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.
Amazon SQS worker log:
2026-04-27T14:02:11Z Received messageId=82f3a9 paymentId=78341 receiveCount=1
2026-04-27T14:02:57Z Charged card successfully for paymentId=78341
2026-04-27T14:03:05Z Timeout occurred before DeleteMessage
2026-04-27T14:03:12Z Received messageId=82f3a9 paymentId=78341 receiveCount=2
2026-04-27T14:03:43Z Duplicate charge blocked manually
Queue configuration:
VisibilityTimeout=30 seconds
RedrivePolicy=not configured
A
Switch the queue to FIFO and rely on content-based deduplication to guarantee exactly-once processing.
Why wrong: FIFO deduplication helps within its deduplication window, but it does not eliminate all duplicate-processing cases after application retries or external side effects.
B
Make the consumer idempotent by storing a processed payment key and rejecting repeat charges.
The worker can still receive the same message more than once because SQS Standard is at-least-once delivery and the delete happened after the charge. Idempotency is the correct safety control because it prevents the payment from being applied twice even when the message is retried. A processed-payment record or conditional write lets retries remain possible without creating duplicate charges.
C
Reduce the visibility timeout so the message becomes available again sooner after a timeout.
Why wrong: A shorter visibility timeout increases the chance of duplicate delivery and does not protect the payment system from repeated side effects.
D
Add a dead-letter queue and disable retries so the message is never processed twice.
Why wrong: A DLQ is useful for poison messages, but disabling retries would increase message loss and still would not solve duplicates caused before deletion.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Make the consumer idempotent by storing a processed payment key and rejecting repeat charges.
Option B is correct because making the consumer idempotent ensures that even if the same message is processed more than once (due to a timeout after the charge is submitted but before the message is deleted), the duplicate charge will be rejected. By storing a processed payment key (e.g., a unique transaction ID) and checking it before processing, the system can safely retry without causing duplicate payments. This approach preserves retry behavior while preventing duplicates, which is the core requirement.
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.
✗
Switch the queue to FIFO and rely on content-based deduplication to guarantee exactly-once processing.
Why it's wrong here
FIFO deduplication helps within its deduplication window, but it does not eliminate all duplicate-processing cases after application retries or external side effects.
✓
Make the consumer idempotent by storing a processed payment key and rejecting repeat charges.
Why this is correct
The worker can still receive the same message more than once because SQS Standard is at-least-once delivery and the delete happened after the charge. Idempotency is the correct safety control because it prevents the payment from being applied twice even when the message is retried. A processed-payment record or conditional write lets retries remain possible without creating duplicate charges.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Reduce the visibility timeout so the message becomes available again sooner after a timeout.
Why it's wrong here
A shorter visibility timeout increases the chance of duplicate delivery and does not protect the payment system from repeated side effects.
✗
Add a dead-letter queue and disable retries so the message is never processed twice.
Why it's wrong here
A DLQ is useful for poison messages, but disabling retries would increase message loss and still would not solve duplicates caused before deletion.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume FIFO queues with deduplication guarantee exactly-once processing, but they fail to recognize that deduplication only prevents duplicate message delivery, not duplicate processing when the consumer times out after processing but before acknowledging the message.
Detailed technical explanation
How to think about this question
Idempotency in distributed systems is typically implemented using a unique identifier (e.g., a payment ID or idempotency key) stored in a database with a unique constraint or in a cache like Redis with a TTL. When a consumer receives a message, it first checks if the key exists; if it does, it skips processing (or returns success), ensuring that retries do not cause side effects. This pattern is critical in payment systems where network partitions or timeouts can lead to duplicate requests, and it aligns with the AWS Well-Architected Framework's reliability pillar.
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
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
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: Make the consumer idempotent by storing a processed payment key and rejecting repeat charges. — Option B is correct because making the consumer idempotent ensures that even if the same message is processed more than once (due to a timeout after the charge is submitted but before the message is deleted), the duplicate charge will be rejected. By storing a processed payment key (e.g., a unique transaction ID) and checking it before processing, the system can safely retry without causing duplicate payments. This approach preserves retry behavior while preventing duplicates, which is the core requirement.
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 →
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. A service processes customer payments from a message queue. Because the queue provides at-least-once delivery, the same payment message can be delivered more than once if the consumer times out before committing its state. Currently, the service sometimes charges the customer twice.
Which design change most directly prevents duplicate charges while still allowing safe retries?
medium
A.Delete the message from the queue immediately after receive to prevent redelivery.
✓ B.Make the payment processing idempotent by recording an idempotency key for each payment and ensuring repeated deliveries do not apply the charge twice.
C.Increase the queue visibility timeout to a very large value so messages rarely reappear.
D.Switch to a single-threaded consumer with one worker so messages are processed in order.
Why B: Option B is correct because making payment processing idempotent using an idempotency key ensures that even if the same message is delivered multiple times due to at-least-once delivery semantics, the charge is applied only once. The consumer records a unique key (e.g., payment ID) in a durable store (like DynamoDB or Redis) and checks it before processing; if the key already exists, the charge is skipped. This directly prevents duplicate charges while still allowing safe retries, as the consumer can safely reprocess messages without side effects.
Variation 2. Based on the exhibit, the payment worker sometimes processes the same SQS Standard message more than once after a timeout. What change best prevents duplicate charges while keeping the queue architecture?
medium
A.Increase the SQS visibility timeout to 15 minutes and leave the worker unchanged.
B.Replace the Standard queue with a FIFO queue and rely only on message ordering.
✓ C.Make the payment workflow idempotent by recording a unique order key before charging.
D.Add a second consumer so duplicate messages are processed faster.
Why C: Option C is correct because making the payment workflow idempotent ensures that even if the same SQS Standard message is processed more than once (due to a visibility timeout), the duplicate charge is prevented by checking a unique order key before processing. This is the most robust solution for handling at-least-once delivery semantics of Standard queues without changing the queue architecture.
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.
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.
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.
Sign in to join the discussion.