Question 466 of 1,040
Design Resilient ArchitecturesmediumMultiple ChoiceObjective-mapped

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. A key principle to apply: lambda asynchronous invocations retry twice by default.. 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 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.

Question 1mediummultiple choice
Read the full NAT/PAT explanation →

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

A Lambda dead-letter queue or failure destination

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.

Key principle: Lambda asynchronous invocations retry twice by default.

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 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

    Lambda asynchronous invocations retry twice by default.

  • 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.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse Lambda DLQs with SQS DLQs or assume that increasing retries (via reserved concurrency or package size) solves the retention problem, but the key is the explicit configuration to capture events after retries are exhausted.

Detailed technical explanation

How to think about this question

Lambda DLQs work by routing the event payload to a specified SQS queue or SNS topic after all retry attempts (up to 3 by default) are exhausted. The event is sent as-is, preserving the original invocation context. Failure destinations, introduced later, provide a more flexible mechanism that can also capture success events and integrate with EventBridge, but both serve the same core purpose for failed events. Under the hood, Lambda uses the AWS SDK to asynchronously publish the event to the destination, ensuring durability even if the destination is temporarily unavailable.

KKey Concepts to Remember

  • Lambda asynchronous invocations retry twice by default.
  • A DLQ (SQS or SNS) captures events that fail after all retries.
  • Failure destinations provide more detailed context than traditional DLQs.
  • DLQs are essential for retaining failed events for later analysis and reprocessing.

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

Lambda asynchronous invocations retry twice by default.

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 lambda asynchronous invocations retry twice by default., then practise related SAA-C03 questions on the same topic to reinforce the concept.

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.

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 — Lambda asynchronous invocations retry twice by default..

What is the correct answer to this question?

The correct answer is: A Lambda dead-letter queue or failure destination — 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.

What should I do if I get this SAA-C03 question wrong?

Review lambda asynchronous invocations retry twice by default., then practise related SAA-C03 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Lambda asynchronous invocations retry twice by default.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SAA-C03 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.