- A
Implement idempotent processing (for example, store processed payment IDs in DynamoDB) and configure an SQS dead-letter queue (DLQ) using a redrive policy with an appropriate maxReceiveCount.
With SQS Standard’s at-least-once delivery, duplicates can occur. Idempotency ensures repeated processing of the same payment ID does not create duplicate side effects. A DLQ with redrive policy isolates poison messages: after a message is received and fails processing more than maxReceiveCount times, SQS moves it to the DLQ instead of cycling it back to the main queue indefinitely.
- B
Rely only on increasing the SQS visibility timeout so duplicates rarely occur, without adding idempotency checks or a DLQ.
Why wrong: Increasing visibility timeout reduces how often duplicates happen, but it cannot guarantee elimination (timeouts, crashes, or long-tail processing delays can still cause re-delivery). It also does not handle poison messages that consistently fail.
- C
Switch to a FIFO queue and delete messages immediately upon receipt to avoid duplicates.
Why wrong: Deleting immediately removes the ability to retry safely. If processing fails after deletion, the payment order may never be processed, causing lost or inconsistent outcomes.
- D
Move the workload to SNS and use synchronous HTTP endpoints so the sender retries until the receiver confirms success.
Why wrong: SNS delivery is not a guaranteed exactly-once request/response mechanism. Even with retry behavior, duplicate deliveries and partial failures can still occur, and this approach does not directly provide the same DLQ + idempotency protections for at-least-once delivery semantics.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
A payments service receives payment orders by consuming messages from an Amazon SQS Standard queue. The downstream processor occasionally exceeds its processing timeout. As a result, some messages reappear in the queue and may be processed more than once.
The team wants to prevent duplicate side effects (for example, double-charging) and also ensure poison messages do not repeatedly consume processing capacity.
What approach best satisfies both goals?
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
Implement idempotent processing (for example, store processed payment IDs in DynamoDB) and configure an SQS dead-letter queue (DLQ) using a redrive policy with an appropriate maxReceiveCount.
Option A is correct because it addresses both requirements: idempotent processing (e.g., storing processed payment IDs in DynamoDB) ensures that even if a message is processed more than once, duplicate side effects like double-charging are prevented. Configuring an SQS dead-letter queue (DLQ) with a redrive policy and an appropriate maxReceiveCount (e.g., 3 or 5) automatically moves messages that exceed the maximum number of receives to the DLQ, preventing poison messages from repeatedly consuming processing capacity.
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.
- ✓
Implement idempotent processing (for example, store processed payment IDs in DynamoDB) and configure an SQS dead-letter queue (DLQ) using a redrive policy with an appropriate maxReceiveCount.
Why this is correct
With SQS Standard’s at-least-once delivery, duplicates can occur. Idempotency ensures repeated processing of the same payment ID does not create duplicate side effects. A DLQ with redrive policy isolates poison messages: after a message is received and fails processing more than maxReceiveCount times, SQS moves it to the DLQ instead of cycling it back to the main queue indefinitely.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Rely only on increasing the SQS visibility timeout so duplicates rarely occur, without adding idempotency checks or a DLQ.
Why it's wrong here
Increasing visibility timeout reduces how often duplicates happen, but it cannot guarantee elimination (timeouts, crashes, or long-tail processing delays can still cause re-delivery). It also does not handle poison messages that consistently fail.
When this WOULD be correct
This option would be correct in a scenario where the processing time is consistently predictable and the only concern is to avoid temporary overlaps, with no requirement for duplicate prevention or poison message handling.
- ✗
Switch to a FIFO queue and delete messages immediately upon receipt to avoid duplicates.
Why it's wrong here
Deleting immediately removes the ability to retry safely. If processing fails after deletion, the payment order may never be processed, causing lost or inconsistent outcomes.
When this WOULD be correct
A question where the requirement is to process messages in strict order without duplicates, and the processing is idempotent or the message is deleted only after successful processing (e.g., using a FIFO queue with a consumer that deletes after processing and a DLQ for failures).
- ✗
Move the workload to SNS and use synchronous HTTP endpoints so the sender retries until the receiver confirms success.
Why it's wrong here
SNS delivery is not a guaranteed exactly-once request/response mechanism. Even with retry behavior, duplicate deliveries and partial failures can still occur, and this approach does not directly provide the same DLQ + idempotency protections for at-least-once delivery semantics.
When this WOULD be correct
This option would be correct in a scenario where the team needs to fan out messages to multiple subscribers and requires immediate, synchronous confirmation of processing, with no concern for duplicate prevention or poison message handling.
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.
✓Implement idempotent processing (for example, store processed payment IDs in DynamoDB) and configure an SQS dead-letter queue (DLQ) using a redrive policy with an appropriate maxReceiveCount.Correct answer▾
Why this is correct
With SQS Standard’s at-least-once delivery, duplicates can occur. Idempotency ensures repeated processing of the same payment ID does not create duplicate side effects. A DLQ with redrive policy isolates poison messages: after a message is received and fails processing more than maxReceiveCount times, SQS moves it to the DLQ instead of cycling it back to the main queue indefinitely.
✗Rely only on increasing the SQS visibility timeout so duplicates rarely occur, without adding idempotency checks or a DLQ.Wrong answer — click to see why▾
Why this is wrong here
Increasing visibility timeout reduces duplicates but does not guarantee idempotency; messages can still be processed multiple times if the timeout is exceeded. It also fails to handle poison messages that repeatedly fail processing.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the processing time is consistently predictable and the only concern is to avoid temporary overlaps, with no requirement for duplicate prevention or poison message handling.
Why candidates choose this
Candidates may think that increasing visibility timeout is a simple fix to prevent duplicates, overlooking the need for idempotency and poison message management.
✗Switch to a FIFO queue and delete messages immediately upon receipt to avoid duplicates.Wrong answer — click to see why▾
Why this is wrong here
FIFO queues guarantee exactly-once processing, but the question states messages reappear due to processing timeout; deleting immediately upon receipt would lose messages that fail processing, and FIFO does not prevent duplicate side effects if processing is not idempotent.
★ When this WOULD be the correct answer
A question where the requirement is to process messages in strict order without duplicates, and the processing is idempotent or the message is deleted only after successful processing (e.g., using a FIFO queue with a consumer that deletes after processing and a DLQ for failures).
Why candidates choose this
Candidates may think FIFO queues eliminate duplicates entirely, but they only prevent duplicates during delivery, not during processing; they also overlook the need for idempotency and poison message handling.
✗Move the workload to SNS and use synchronous HTTP endpoints so the sender retries until the receiver confirms success.Wrong answer — click to see why▾
Why this is wrong here
SNS with synchronous HTTP endpoints does not guarantee exactly-once processing; the sender may still retry, and the receiver could process duplicates. It also lacks a mechanism to handle poison messages that repeatedly fail, as there is no dead-letter queue.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the team needs to fan out messages to multiple subscribers and requires immediate, synchronous confirmation of processing, with no concern for duplicate prevention or poison message handling.
Why candidates choose this
Candidates may think synchronous processing eliminates duplicates because the sender waits for a response, but they overlook that retries can still cause duplicates, and there is no built-in poison message handling.
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 confuse 'exactly-once delivery' (FIFO queues) with 'exactly-once processing,' failing to realize that idempotency is still required to handle failures after message receipt, and that a DLQ is necessary to manage poison messages regardless of queue type.
Detailed technical explanation
How to think about this question
Under the hood, SQS Standard queues offer at-least-once delivery, meaning duplicates can occur due to network timeouts or processing timeouts. Idempotency via a DynamoDB table with a TTL on the payment ID ensures that only the first successful processing takes effect, while subsequent attempts are ignored. The DLQ redrive policy uses the maxReceiveCount attribute; when a message is received more than that count (e.g., 5), SQS automatically moves it to the DLQ, isolating poison messages for later analysis and preventing them from consuming worker resources indefinitely.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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 — 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 — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement idempotent processing (for example, store processed payment IDs in DynamoDB) and configure an SQS dead-letter queue (DLQ) using a redrive policy with an appropriate maxReceiveCount. — Option A is correct because it addresses both requirements: idempotent processing (e.g., storing processed payment IDs in DynamoDB) ensures that even if a message is processed more than once, duplicate side effects like double-charging are prevented. Configuring an SQS dead-letter queue (DLQ) with a redrive policy and an appropriate maxReceiveCount (e.g., 3 or 5) automatically moves messages that exceed the maximum number of receives to the DLQ, preventing poison messages from repeatedly consuming processing capacity.
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 →
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
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.