- A
Keep the queue as SQS Standard but increase the visibility timeout so duplicates are less likely to reappear during timeouts.
Why wrong: Increasing visibility timeout only delays redelivery. If DeleteMessage fails, the message can still become visible again and be processed again.
- B
Change the queue to an SQS FIFO queue and use a stable deduplication ID derived from the payment instruction ID.
Why wrong: FIFO deduplication reduces duplicate sends within the deduplication window, but it does not prevent a message already in flight from being redelivered after the visibility timeout if it was not deleted.
- C
Make the downstream processor idempotent by recording processed payment instruction IDs in a durable datastore and ignoring repeats.
SQS Standard is at-least-once delivery, so the same message can be delivered more than once if the consumer times out before deleting it. Idempotent processing is the strongest protection against duplicate side effects because it prevents repeat application of the payment even when the message is redelivered.
- D
Use an ALB health check to restart the downstream processor when timeouts occur.
Why wrong: Restarting the processor may help availability, but it does not change SQS delivery semantics or prevent a redelivered message from causing duplicate side effects.
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: idempotency ensures an operation can be applied multiple times without changing the result.. 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. The downstream processor sometimes times out after it has already applied the payment, but before it can delete the message from the queue. As a result, the same payment instruction can be processed more than once. The team wants the strongest way to prevent duplicate side effects while keeping the system decoupled. What should they implement?
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 downstream processor idempotent by recording processed payment instruction IDs in a durable datastore and ignoring repeats.
Option C is correct because making the downstream processor idempotent ensures that duplicate payment instructions are safely ignored, even if the same message is delivered more than once. This approach provides the strongest guarantee against duplicate side effects without requiring changes to the queue type or increasing visibility timeouts, and it keeps the system fully decoupled.
Key principle: Idempotency ensures an operation can be applied multiple times without changing the result.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Keep the queue as SQS Standard but increase the visibility timeout so duplicates are less likely to reappear during timeouts.
Why it's wrong here
Increasing visibility timeout only delays redelivery. If DeleteMessage fails, the message can still become visible again and be processed again.
- ✗
Change the queue to an SQS FIFO queue and use a stable deduplication ID derived from the payment instruction ID.
Why it's wrong here
FIFO deduplication reduces duplicate sends within the deduplication window, but it does not prevent a message already in flight from being redelivered after the visibility timeout if it was not deleted.
- ✓
Make the downstream processor idempotent by recording processed payment instruction IDs in a durable datastore and ignoring repeats.
Why this is correct
SQS Standard is at-least-once delivery, so the same message can be delivered more than once if the consumer times out before deleting it. Idempotent processing is the strongest protection against duplicate side effects because it prevents repeat application of the payment even when the message is redelivered.
Related concept
Idempotency ensures an operation can be applied multiple times without changing the result.
- ✗
Use an ALB health check to restart the downstream processor when timeouts occur.
Why it's wrong here
Restarting the processor may help availability, but it does not change SQS delivery semantics or prevent a redelivered message from causing duplicate side effects.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume that switching to a FIFO queue or increasing visibility timeout fully solves duplicate processing, but they overlook that the downstream processor's timeout after applying the payment is the root cause, which idempotency directly addresses.
Detailed technical explanation
How to think about this question
Idempotency is achieved by storing a unique key (e.g., payment instruction ID) in a durable datastore like DynamoDB or Redis, and checking it before processing each message. Under the hood, this pattern ensures that even if the same message is delivered multiple times due to at-least-once delivery semantics, the side effect (e.g., applying a payment) occurs only once. In a real-world scenario, this is critical for financial transactions where duplicate charges must be avoided, and it decouples the retry logic from the queue configuration.
KKey Concepts to Remember
- Idempotency ensures an operation can be applied multiple times without changing the result.
- It is crucial for 'at-least-once' delivery systems like SQS Standard queues.
- Implementing idempotency typically involves storing unique transaction IDs in a durable datastore.
- Idempotent processors check for existing IDs before executing side effects.
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
Idempotency ensures an operation can be applied multiple times without changing the result.
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.
Review idempotency ensures an operation can be applied multiple times without changing the result., 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 — Idempotency ensures an operation can be applied multiple times without changing the result..
What is the correct answer to this question?
The correct answer is: Make the downstream processor idempotent by recording processed payment instruction IDs in a durable datastore and ignoring repeats. — Option C is correct because making the downstream processor idempotent ensures that duplicate payment instructions are safely ignored, even if the same message is delivered more than once. This approach provides the strongest guarantee against duplicate side effects without requiring changes to the queue type or increasing visibility timeouts, and it keeps the system fully decoupled.
What should I do if I get this SAA-C03 question wrong?
Review idempotency ensures an operation can be applied multiple times without changing the result., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Idempotency ensures an operation can be applied multiple times without changing the result.
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.