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?
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
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.
When this WOULD be correct
A question where the requirement is to guarantee exactly-once delivery of messages in a distributed system, and the application can tolerate a 5-minute deduplication window. For example: 'A financial application must ensure that payment requests are processed exactly once, even if the producer sends duplicate messages. Which queue type should be used?'
✓
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.
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.
When this WOULD be correct
This option would be correct in a scenario where the goal is to minimize latency for retrying failed messages, and duplicate processing is acceptable or handled elsewhere. For example, a question asking 'How to ensure a message is retried quickly after a worker failure?' would make reducing visibility timeout the best answer.
✗
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.
When this WOULD be correct
A question where the requirement is to prevent duplicate processing of poison-pill messages that cannot be handled successfully, and retries are not needed. For example: 'An order processing system fails repeatedly on certain malformed messages. What is the most cost-effective way to isolate these messages for manual inspection without retrying them?'
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Make the consumer idempotent by storing a processed payment key and rejecting repeat charges.Correct answer▾
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.
✗Switch the queue to FIFO and rely on content-based deduplication to guarantee exactly-once processing.Wrong answer — click to see why▾
Why this is wrong here
FIFO queues with content-based deduplication provide exactly-once delivery, but the issue here is a timeout after submission but before deletion, which can still cause duplicate processing if the worker retries. FIFO deduplication does not prevent duplicate charges if the same message is sent again after a timeout, as deduplication is based on message content within a 5-minute window, not on processing state.
★ When this WOULD be the correct answer
A question where the requirement is to guarantee exactly-once delivery of messages in a distributed system, and the application can tolerate a 5-minute deduplication window. For example: 'A financial application must ensure that payment requests are processed exactly once, even if the producer sends duplicate messages. Which queue type should be used?'
Why candidates choose this
Candidates often associate FIFO queues with exactly-once processing and assume that deduplication solves all duplicate issues, without considering that the duplicate here arises from a retry after a timeout, not from duplicate message sends.
✗Reduce the visibility timeout so the message becomes available again sooner after a timeout.Wrong answer — click to see why▾
Why this is wrong here
Reducing the visibility timeout would cause the message to reappear sooner after a timeout, increasing the likelihood of duplicate processing rather than preventing it. It does not address the root cause of duplicate charges when the worker times out after submitting the charge.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the goal is to minimize latency for retrying failed messages, and duplicate processing is acceptable or handled elsewhere. For example, a question asking 'How to ensure a message is retried quickly after a worker failure?' would make reducing visibility timeout the best answer.
Why candidates choose this
Candidates may think that making the message available again faster will reduce the chance of duplicate charges by allowing the worker to delete the message before a new attempt, but they overlook that the duplicate charge has already occurred before the timeout.
✗Add a dead-letter queue and disable retries so the message is never processed twice.Wrong answer — click to see why▾
Why this is wrong here
Adding a dead-letter queue and disabling retries prevents duplicate charges by eliminating retries, but the question explicitly requires keeping retry behavior. This option removes retries, which violates the requirement.
★ When this WOULD be the correct answer
A question where the requirement is to prevent duplicate processing of poison-pill messages that cannot be handled successfully, and retries are not needed. For example: 'An order processing system fails repeatedly on certain malformed messages. What is the most cost-effective way to isolate these messages for manual inspection without retrying them?'
Why candidates choose this
Candidates may think that a dead-letter queue is a standard solution for preventing duplicates, and disabling retries seems like a direct way to avoid reprocessing, overlooking the explicit requirement to retain retry behavior.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
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.
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 →
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.