- A
Set the SQS visibility timeout extremely long so the message cannot be retried even after processing failures.
Why wrong: A long visibility timeout only delays retries. If a consumer fails after partial work, duplicates still occur later, and recovery becomes slower and riskier for real failures.
- B
Make the consumer idempotent by deriving a deterministic idempotency key from the payment instruction (for example, the instruction ID), persisting the result of successful processing, and skipping re-processing when that key is already marked successful.
SQS Standard provides at-least-once delivery, so duplicates are expected. Idempotency ensures that re-processing the same instruction does not create incorrect side effects. Persisting a deterministic key/result allows the consumer to safely short-circuit duplicates after retries/timeouts.
- C
Switch to an SQS FIFO queue but remove error handling in the consumer so duplicates never occur.
Why wrong: FIFO can change ordering and reduce some duplicate scenarios, but it does not eliminate duplicates in all failure modes. Removing error handling reduces resiliency and can lead to lost or inconsistent processing.
- D
Send all failed messages to a DLQ and rely on it to deduplicate messages that were already successfully processed.
Why wrong: A DLQ captures messages that fail repeatedly (after retry attempts / redrive conditions). It is for poison-message handling, not for deduplicating messages that were already successfully processed but later retried.
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. A key principle to apply: sQS Standard queues offer at-least-once message delivery.. 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.
An orders service publishes payment instructions to an Amazon SQS Standard queue. A downstream consumer sometimes times out or crashes after it has partially completed processing, causing the same instruction to be processed more than once. You must keep the design resilient without attempting to guarantee exactly-once processing. Which approach best handles duplicates safely?
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.
Answer choices
Why each option matters
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 deriving a deterministic idempotency key from the payment instruction (for example, the instruction ID), persisting the result of successful processing, and skipping re-processing when that key is already marked successful.
Option B is correct because making the consumer idempotent ensures that even if the same payment instruction is processed multiple times due to timeouts or crashes, the system remains consistent. By deriving a deterministic idempotency key (e.g., the instruction ID) and persisting the result of successful processing, the consumer can skip re-processing when the key is already marked as successful. This approach aligns with the requirement to keep the design resilient without guaranteeing exactly-once processing, as it safely handles duplicates at the application level.
Key principle: SQS Standard queues offer at-least-once message delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set the SQS visibility timeout extremely long so the message cannot be retried even after processing failures.
Why it's wrong here
A long visibility timeout only delays retries. If a consumer fails after partial work, duplicates still occur later, and recovery becomes slower and riskier for real failures.
- ✓
Make the consumer idempotent by deriving a deterministic idempotency key from the payment instruction (for example, the instruction ID), persisting the result of successful processing, and skipping re-processing when that key is already marked successful.
Why this is correct
SQS Standard provides at-least-once delivery, so duplicates are expected. Idempotency ensures that re-processing the same instruction does not create incorrect side effects. Persisting a deterministic key/result allows the consumer to safely short-circuit duplicates after retries/timeouts.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
SQS Standard queues offer at-least-once message delivery.
- ✗
Switch to an SQS FIFO queue but remove error handling in the consumer so duplicates never occur.
Why it's wrong here
FIFO can change ordering and reduce some duplicate scenarios, but it does not eliminate duplicates in all failure modes. Removing error handling reduces resiliency and can lead to lost or inconsistent processing.
- ✗
Send all failed messages to a DLQ and rely on it to deduplicate messages that were already successfully processed.
Why it's wrong here
A DLQ captures messages that fail repeatedly (after retry attempts / redrive conditions). It is for poison-message handling, not for deduplicating messages that were already successfully processed but later retried.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume SQS FIFO queues or DLQs inherently solve duplicate processing, but the exam tests understanding that Standard queues require application-level idempotency for safe duplicate handling, and FIFO queues do not eliminate the need for idempotent consumers in crash scenarios.
Trap categories for this question
Scenario analysis trap
FIFO can change ordering and reduce some duplicate scenarios, but it does not eliminate duplicates in all failure modes. Removing error handling reduces resiliency and can lead to lost or inconsistent processing.
Detailed technical explanation
How to think about this question
Idempotency in distributed systems is often implemented using a database with a unique constraint on the idempotency key, ensuring that only the first successful write is accepted. In SQS Standard queues, at-least-once delivery means duplicates are inherent, so the consumer must handle them via idempotency rather than relying on the queue itself. A real-world scenario is a payment service where a duplicate charge could cause financial loss; using an idempotency key stored in DynamoDB with conditional writes prevents double processing even if the same message is delivered multiple times.
KKey Concepts to Remember
- SQS Standard queues offer at-least-once message delivery.
- Idempotency ensures an operation can be applied multiple times without changing the result beyond the initial application.
- An idempotency key is derived deterministically from the message content.
- Persisting processing results with the idempotency key prevents re-processing of already completed tasks.
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
SQS Standard queues offer at-least-once message delivery.
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. SQS Standard queues offer at-least-once message delivery. 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.
Review sQS Standard queues offer at-least-once message delivery., then practise related SAA-C03 questions on the same topic to reinforce the concept.
- →
Design Resilient Architectures — study guide chapter
Learn the concepts, then practise the questions
- →
Design Resilient Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
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.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
Design Resilient Architectures — This question tests Design Resilient Architectures — SQS Standard queues offer at-least-once message delivery..
What is the correct answer to this question?
The correct answer is: Make the consumer idempotent by deriving a deterministic idempotency key from the payment instruction (for example, the instruction ID), persisting the result of successful processing, and skipping re-processing when that key is already marked successful. — Option B is correct because making the consumer idempotent ensures that even if the same payment instruction is processed multiple times due to timeouts or crashes, the system remains consistent. By deriving a deterministic idempotency key (e.g., the instruction ID) and persisting the result of successful processing, the consumer can skip re-processing when the key is already marked as successful. This approach aligns with the requirement to keep the design resilient without guaranteeing exactly-once processing, as it safely handles duplicates at the application level.
What should I do if I get this SAA-C03 question wrong?
Review sQS Standard queues offer at-least-once message delivery., then practise related SAA-C03 questions on the same topic to reinforce the concept.
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?
SQS Standard queues offer at-least-once message delivery.
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 →
Last reviewed: Jun 11, 2026
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.