The answer is to configure a Lambda dead-letter queue or failure destination. This is correct because when a Lambda function processes events asynchronously from services like S3 or SNS, it automatically retries failed invocations twice, but once those retries are exhausted, the event is discarded unless you explicitly capture it. A dead-letter queue, typically an SQS queue or SNS topic, acts as a safety net to retain those failed events for later investigation, giving you enforceable control during normal operations without blocking the function’s ongoing processing. On the SAA-C03 exam, this scenario tests your understanding of asynchronous invocation error handling and the distinction between synchronous and asynchronous patterns—a common trap is confusing DLQs with synchronous retry mechanisms like API Gateway or Step Functions. Remember the memory tip: “After retries die, the DLQ catches the cry”—meaning once retries are exhausted, the dead-letter queue preserves the failed event for forensic analysis.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. A key principle to apply: dLQs/failure destinations capture events after all asynchronous retries fail.. 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 content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured? The team wants the control to be enforceable during normal operations.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A Lambda dead-letter queue or failure destination
Option D is correct because a Lambda dead-letter queue (DLQ) or failure destination allows you to capture events that have exhausted all retry attempts from an asynchronous invocation. This ensures failed events are retained in Amazon SQS or SNS for later investigation, providing enforceable control during normal operations without impacting the function's ability to process successful events.
Key principle: DLQs/failure destinations capture events after all asynchronous retries fail.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Lambda reserved concurrency set to zero
Why it's wrong here
Reserved concurrency of zero stops processing and does not preserve failed events as an error-handling strategy.
✗
A larger deployment package
Why it's wrong here
Package size does not affect failed-event capture.
✗
CloudFront error pages
Why it's wrong here
CloudFront does not manage Lambda asynchronous retry failures.
✓
A Lambda dead-letter queue or failure destination
Why this is correct
A DLQ or asynchronous failure destination captures failed events after retry attempts.
Related concept
DLQs/failure destinations capture events after all asynchronous retries fail.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse Lambda's synchronous invocation error handling (where DLQs are not supported) with asynchronous invocation, or mistakenly think that increasing function resources (like deployment package size) can improve reliability against external API failures.
Detailed technical explanation
How to think about this question
Lambda's asynchronous invocation mode automatically retries failed invocations twice (for a total of three attempts) before discarding the event unless a DLQ or failure destination is configured. A DLQ (Amazon SQS or SNS) captures the event payload after retries are exhausted, while a failure destination can route the event to another Lambda, SQS, SNS, or EventBridge for custom processing. This mechanism is critical for building resilient serverless workflows where transient third-party API failures must be investigated without data loss.
KKey Concepts to Remember
DLQs/failure destinations capture events after all asynchronous retries fail.
They can be an SQS queue or an SNS topic.
Configured directly on the Lambda function's asynchronous invocation settings.
Preserves the original event payload for later investigation.
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
DLQs/failure destinations capture events after all asynchronous retries fail.
Real-world example
How this comes up in practice
A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
What to study next
Got this wrong? Here's your next step.
Review dLQs/failure destinations capture events after all asynchronous retries fail., then practise related SAA-C03 questions on the same topic to reinforce the concept.
Design Resilient Architectures — This question tests Design Resilient Architectures — DLQs/failure destinations capture events after all asynchronous retries fail..
What is the correct answer to this question?
The correct answer is: A Lambda dead-letter queue or failure destination — Option D is correct because a Lambda dead-letter queue (DLQ) or failure destination allows you to capture events that have exhausted all retry attempts from an asynchronous invocation. This ensures failed events are retained in Amazon SQS or SNS for later investigation, providing enforceable control during normal operations without impacting the function's ability to process successful events.
What should I do if I get this SAA-C03 question wrong?
Review dLQs/failure destinations capture events after all asynchronous retries fail., then practise related SAA-C03 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
DLQs/failure destinations capture events after all asynchronous retries fail.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured?
medium
A.Lambda reserved concurrency set to zero
B.A larger deployment package
C.CloudFront error pages
✓ D.A Lambda dead-letter queue or failure destination
Why D: A Lambda dead-letter queue (DLQ) or failure destination captures events that have exhausted all retry attempts, preserving them in Amazon SQS or SNS for later investigation. This ensures failed invocations from the unreliable third-party API are not lost and can be analyzed or replayed, meeting the requirement for retention after retries are exhausted.
Variation 2. A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured? The architecture review board prefers a managed AWS-native control.
medium
A.Lambda reserved concurrency set to zero
B.A larger deployment package
C.CloudFront error pages
✓ D.A Lambda dead-letter queue or failure destination
Why D: Option D is correct because Lambda dead-letter queues (DLQs) or failure destinations are the managed AWS-native way to capture events that have exhausted all retry attempts from an asynchronous invocation. When the Lambda function fails after the configured number of retries (default 3), the event is automatically sent to an SQS queue or SNS topic (DLQ) or to a specified destination (e.g., SQS, SNS, EventBridge) for later investigation and reprocessing.
Variation 3. A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured? The design must avoid adding custom operational scripts.
medium
A.Lambda reserved concurrency set to zero
B.A larger deployment package
C.CloudFront error pages
✓ D.A Lambda dead-letter queue or failure destination
Why D: A Lambda dead-letter queue (DLQ) or failure destination is the correct solution because it captures events that have exhausted all retry attempts from an asynchronous Lambda invocation. This allows failed events to be retained in an Amazon SQS queue or SNS topic for later investigation, without requiring custom operational scripts. The DLQ or failure destination integrates directly with Lambda's built-in retry behavior, ensuring that only events that fail after the configured number of retries are sent to the destination.
Variation 4. A inventory service uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured?
medium
A.Lambda reserved concurrency set to zero
✓ B.A Lambda dead-letter queue or failure destination
C.A larger deployment package
D.CloudFront error pages
Why B: Lambda dead-letter queues (DLQs) or failure destinations are the correct mechanism to retain failed events after all retries are exhausted. When a Lambda function fails to process an event (e.g., from an asynchronous invocation), the service automatically retries twice. If those retries fail, the event can be sent to an SQS queue or SNS topic (DLQ) or to a specified destination (failure destination) for later investigation. This ensures no data loss and provides a durable storage for post-mortem analysis.
Variation 5. A inventory service uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured? The design must avoid adding custom operational scripts.
medium
A.Lambda reserved concurrency set to zero
✓ B.A Lambda dead-letter queue or failure destination
C.A larger deployment package
D.CloudFront error pages
Why B: A Lambda dead-letter queue (DLQ) or failure destination allows you to capture events that have exhausted all retry attempts from an asynchronous invocation. When the Lambda function fails after the maximum retries (default 3), the event is sent to the configured SQS queue or SNS topic for later investigation, without requiring custom scripts or manual polling.
Variation 6. A inventory service uses Lambda functions that call an unreliable third-party API. Failed events must be retained for later investigation after retries are exhausted. What should be configured? The architecture review board prefers a managed AWS-native control.
medium
A.Lambda reserved concurrency set to zero
✓ B.A Lambda dead-letter queue or failure destination
C.A larger deployment package
D.CloudFront error pages
Why B: Lambda dead-letter queues (DLQs) or failure destinations are the correct AWS-native mechanism to retain failed events after retries are exhausted. When a Lambda function fails to process an event (e.g., due to an unreliable third-party API), the function can be configured to send the failed event payload to an SQS queue or SNS topic for later investigation. This ensures no data loss and aligns with the requirement for a managed, AWS-native solution.
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.