- A
Set the SQS queue’s retention period to 10 years and rely on application retries to eventually succeed.
Why wrong: Retention affects how long messages remain available, but it doesn’t isolate repeatedly failing messages.
- B
Increase visibility timeout to a very large value and avoid dead-letter queues to keep ordering stable.
Why wrong: Long visibility time can delay failures, but it does not provide dead-letter isolation for poison messages.
- C
Configure a redrive policy with a dead-letter queue (DLQ) and set an appropriate visibility timeout greater than the maximum processing time.
A DLQ isolates poison messages after a receive count threshold, and correct visibility timeout prevents premature retries.
- D
Switch the queue to FIFO and remove retries in the Lambda event source mapping entirely.
Why wrong: FIFO and disabling retries do not reliably solve poison message isolation without DLQ-based redriving.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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.
An order processing workflow uses Amazon SQS as the decoupling layer between a producer and a consumer Lambda function. The consumer intermittently fails due to a downstream dependency. The team has observed that certain “poison” messages keep being retried repeatedly and prevent other messages from being processed efficiently. Which SQS configuration most directly addresses this issue?
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
Configure a redrive policy with a dead-letter queue (DLQ) and set an appropriate visibility timeout greater than the maximum processing time.
Option C is correct because configuring a redrive policy with a dead-letter queue (DLQ) allows messages that repeatedly fail processing to be moved out of the main queue after a specified number of receive attempts. Setting an appropriate visibility timeout greater than the maximum processing time ensures that messages are not made visible again before the consumer finishes processing, preventing premature retries. This directly isolates poison messages so they no longer block the processing of other messages in the queue.
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.
- ✗
Set the SQS queue’s retention period to 10 years and rely on application retries to eventually succeed.
Why it's wrong here
Retention affects how long messages remain available, but it doesn’t isolate repeatedly failing messages.
When this WOULD be correct
If the question asked for ensuring message durability for long-term processing where failures are transient and no poison messages exist, setting a long retention period would be correct.
- ✗
Increase visibility timeout to a very large value and avoid dead-letter queues to keep ordering stable.
Why it's wrong here
Long visibility time can delay failures, but it does not provide dead-letter isolation for poison messages.
When this WOULD be correct
In a scenario where message ordering is critical and you cannot tolerate any message loss or reordering, and you have a mechanism to ensure all messages eventually succeed (e.g., idempotent processing with exponential backoff), you might avoid DLQs and use a very large visibility timeout to prevent premature retries.
- ✓
Configure a redrive policy with a dead-letter queue (DLQ) and set an appropriate visibility timeout greater than the maximum processing time.
Why this is correct
A DLQ isolates poison messages after a receive count threshold, and correct visibility timeout prevents premature retries.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Switch the queue to FIFO and remove retries in the Lambda event source mapping entirely.
Why it's wrong here
FIFO and disabling retries do not reliably solve poison message isolation without DLQ-based redriving.
When this WOULD be correct
This option would be correct in a scenario where the requirement is to process messages in strict order and any failed message must be discarded immediately to avoid blocking subsequent messages, with no tolerance for retries or reordering.
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.
✓Configure a redrive policy with a dead-letter queue (DLQ) and set an appropriate visibility timeout greater than the maximum processing time.Correct answer▾
Why this is correct
A DLQ isolates poison messages after a receive count threshold, and correct visibility timeout prevents premature retries.
✗Set the SQS queue’s retention period to 10 years and rely on application retries to eventually succeed.Wrong answer — click to see why▾
Why this is wrong here
Setting the retention period to 10 years does not address poison messages; it only keeps messages longer. Relying on application retries without a DLQ allows poison messages to be retried indefinitely, blocking other messages.
★ When this WOULD be the correct answer
If the question asked for ensuring message durability for long-term processing where failures are transient and no poison messages exist, setting a long retention period would be correct.
Why candidates choose this
Candidates may think increasing retention gives more time for retries to succeed, overlooking that poison messages never succeed and need isolation via a DLQ.
✗Increase visibility timeout to a very large value and avoid dead-letter queues to keep ordering stable.Wrong answer — click to see why▾
Why this is wrong here
Increasing visibility timeout to a very large value does not prevent poison messages from blocking the queue; they will still be retried indefinitely, and without a DLQ, failed messages cannot be isolated for analysis or skipped.
★ When this WOULD be the correct answer
In a scenario where message ordering is critical and you cannot tolerate any message loss or reordering, and you have a mechanism to ensure all messages eventually succeed (e.g., idempotent processing with exponential backoff), you might avoid DLQs and use a very large visibility timeout to prevent premature retries.
Why candidates choose this
Candidates may think that a large visibility timeout gives more time for processing and avoids reordering, but they overlook that poison messages will still block the queue and cause repeated failures without a DLQ to divert them.
✗Switch the queue to FIFO and remove retries in the Lambda event source mapping entirely.Wrong answer — click to see why▾
Why this is wrong here
Switching to FIFO and removing retries does not address poison messages; FIFO ensures strict ordering but does not prevent problematic messages from blocking the queue, and removing retries would cause immediate failures without handling the root cause.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the requirement is to process messages in strict order and any failed message must be discarded immediately to avoid blocking subsequent messages, with no tolerance for retries or reordering.
Why candidates choose this
Candidates may think FIFO queues solve all ordering issues and that removing retries simplifies error handling, overlooking that poison messages still need isolation via DLQs and that retries are essential for transient failures.
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 may think increasing visibility timeout or switching to FIFO alone will handle failed messages, but without a DLQ, poison messages remain in the queue and continue to block other messages, which is the core issue described.
Detailed technical explanation
How to think about this question
Under the hood, SQS uses a redrive policy with a `maxReceiveCount` threshold; once a message is received that many times without being deleted, it is automatically moved to the configured DLQ. The visibility timeout must be set to at least the maximum expected processing time of the consumer Lambda, otherwise messages can become visible again while still being processed, leading to duplicate processing and potential race conditions. In real-world scenarios, poison messages often result from transient downstream failures or malformed data, and the DLQ allows operators to inspect and reprocess them manually or via a separate remediation workflow.
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.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
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: Configure a redrive policy with a dead-letter queue (DLQ) and set an appropriate visibility timeout greater than the maximum processing time. — Option C is correct because configuring a redrive policy with a dead-letter queue (DLQ) allows messages that repeatedly fail processing to be moved out of the main queue after a specified number of receive attempts. Setting an appropriate visibility timeout greater than the maximum processing time ensures that messages are not made visible again before the consumer finishes processing, preventing premature retries. This directly isolates poison messages so they no longer block the processing of other messages in the queue.
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.