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 queue
QueueName: payments-standard
QueueType: Standard
VisibilityTimeout: 120 seconds
Worker logs
14:01:10 Received messageId=msg-4412 orderId=4412
14:03:09 Charged customer card successfully
14:03:10 Lambda timed out before DeleteMessage completed
14:03:35 Same message received again and charged a second time
Business requirement
A payment must never be charged twice even if a message is delivered again.
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?
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 queue
QueueName: payments-standard
QueueType: Standard
VisibilityTimeout: 120 seconds
Worker logs
14:01:10 Received messageId=msg-4412 orderId=4412
14:03:09 Charged customer card successfully
14:03:10 Lambda timed out before DeleteMessage completed
14:03:35 Same message received again and charged a second time
Business requirement
A payment must never be charged twice even if a message is delivered again.
A
Increase the SQS visibility timeout to 15 minutes and leave the worker unchanged.
Why wrong: A longer visibility timeout can reduce the chance of a duplicate becoming visible too early, but it does not guarantee correctness. A retry, function timeout, worker crash, or later redelivery can still cause a second charge if the business operation itself is not protected.
B
Replace the Standard queue with a FIFO queue and rely only on message ordering.
Why wrong: FIFO queues help with ordering and can reduce duplicate delivery within a deduplication window, but they do not make an external payment call exactly once by themselves. The application still needs to protect the side effect.
C
Make the payment workflow idempotent by recording a unique order key before charging.
SQS Standard queues are at-least-once delivery, so duplicate messages are always possible. The correct safeguard is idempotency: store a unique order or payment request key, check whether that key has already been processed, and only perform the charge the first time it is seen. Any later delivery is safely ignored.
D
Add a second consumer so duplicate messages are processed faster.
Why wrong: More consumers improve throughput but do not prevent duplicate side effects. Without idempotency, additional consumers can actually increase the chance of race conditions and repeated charges.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Make the payment workflow idempotent by recording a unique order key before charging.
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.
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.
✗
Increase the SQS visibility timeout to 15 minutes and leave the worker unchanged.
Why it's wrong here
A longer visibility timeout can reduce the chance of a duplicate becoming visible too early, but it does not guarantee correctness. A retry, function timeout, worker crash, or later redelivery can still cause a second charge if the business operation itself is not protected.
✗
Replace the Standard queue with a FIFO queue and rely only on message ordering.
Why it's wrong here
FIFO queues help with ordering and can reduce duplicate delivery within a deduplication window, but they do not make an external payment call exactly once by themselves. The application still needs to protect the side effect.
✓
Make the payment workflow idempotent by recording a unique order key before charging.
Why this is correct
SQS Standard queues are at-least-once delivery, so duplicate messages are always possible. The correct safeguard is idempotency: store a unique order or payment request key, check whether that key has already been processed, and only perform the charge the first time it is seen. Any later delivery is safely ignored.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add a second consumer so duplicate messages are processed faster.
Why it's wrong here
More consumers improve throughput but do not prevent duplicate side effects. Without idempotency, additional consumers can actually increase the chance of race conditions and repeated charges.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think increasing the visibility timeout (Option A) or switching to a FIFO queue (Option B) will solve duplicate processing, but they overlook that the root cause is the worker's timeout behavior, which requires application-level idempotency to prevent duplicate charges.
Detailed technical explanation
How to think about this question
Idempotency is achieved by storing a unique identifier (e.g., order ID) in a database with a unique constraint or using a conditional write (e.g., DynamoDB ConditionExpression) so that the charge operation only succeeds once. Under the hood, SQS Standard queues use at-least-once delivery, meaning duplicates can occur due to network retries or visibility timeout expiration; idempotent consumers are the recommended pattern to handle this. In a real-world scenario, a payment gateway might return a success response after a timeout, and the worker retries the charge; idempotency keys prevent double billing.
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 payment workflow idempotent by recording a unique order key before charging. — 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.
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 →
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.