Question 613 of 1,040
Design Resilient ArchitectureshardMultiple ChoiceObjective-mapped

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

Exhibit

Amazon EventBridge rule:
- source: orders.checkout
- target: Lambda function process-orders
- retry policy: default

CloudWatch metrics:
- Invocations: 120/min
- Throttles: 87/min
- ApproximateAgeOfOldestEvent: 900 seconds

Lambda log excerpt:
2026-04-27T18:22:41Z payment API timeout
2026-04-27T18:22:44Z retry attempt 3 failed
2026-04-27T18:22:48Z processing orderId=90118 paused

Business requirement:
No events should be lost during a temporary payment API outage, and the system must absorb bursts instead of failing immediately.

Based on the exhibit, downstream payment timeouts cause EventBridge deliveries to back up and some events are retried until they age out. What change best improves resilience and preserves events during downstream outages?

Exhibit

Amazon EventBridge rule:
- source: orders.checkout
- target: Lambda function process-orders
- retry policy: default

CloudWatch metrics:
- Invocations: 120/min
- Throttles: 87/min
- ApproximateAgeOfOldestEvent: 900 seconds

Lambda log excerpt:
2026-04-27T18:22:41Z payment API timeout
2026-04-27T18:22:44Z retry attempt 3 failed
2026-04-27T18:22:48Z processing orderId=90118 paused

Business requirement:
No events should be lost during a temporary payment API outage, and the system must absorb bursts instead of failing immediately.

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

Put an Amazon SQS queue between EventBridge and the consumer, and have workers drain the queue with a DLQ for poison messages.

Option B is correct because introducing an SQS queue between EventBridge and the consumer decouples the event delivery from the downstream payment API. During outages, events are stored durably in SQS and can be processed later without being lost. A Dead Letter Queue (DLQ) captures events that fail repeatedly, preventing poison messages from blocking the queue and ensuring no events age out due to retry exhaustion.

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.

  • Increase the Lambda timeout so each invocation can wait longer for the payment API.

    Why it's wrong here

    A longer timeout does not provide buffering. If the payment API remains unavailable, invocations stay occupied longer and the backlog becomes harder to drain.

    When this WOULD be correct

    This option would be correct if the question were about a Lambda function that fails due to a slow but eventually successful downstream API, and the goal is to avoid premature timeouts without changing the architecture.

  • Put an Amazon SQS queue between EventBridge and the consumer, and have workers drain the queue with a DLQ for poison messages.

    Why this is correct

    SQS is the right durability and buffering layer for this requirement. EventBridge can publish orders.checkout events to a queue, and workers can consume them at a controlled rate even when the payment API is unavailable. This decouples event ingestion from downstream processing, absorbs bursts, and preserves events until the outage ends. A DLQ provides a safe landing zone for messages that continue to fail after retries so they are not silently dropped.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Switch the target to a Lambda function with reserved concurrency of zero during outages.

    Why it's wrong here

    Reserved concurrency of zero stops processing entirely and does not create durable buffering. It would make the backlog worse and does not satisfy the requirement to preserve events during an outage.

    When this WOULD be correct

    This option would be correct in a scenario where you need to temporarily throttle or stop processing from a specific event source to protect a downstream system from overload, while using a DLQ or retry mechanism to preserve events for later processing.

  • Replace EventBridge with CloudWatch Logs subscriptions so the consumer can poll the log stream later.

    Why it's wrong here

    CloudWatch Logs subscriptions are not a durable application messaging pattern and are not a substitute for queue-based buffering in this scenario.

    When this WOULD be correct

    This option would be correct if the requirement was to archive all events for long-term storage and allow a consumer to process them on its own schedule, with no need for real-time delivery or automatic retries during outages.

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.

Put an Amazon SQS queue between EventBridge and the consumer, and have workers drain the queue with a DLQ for poison messages.Correct answer

Why this is correct

SQS is the right durability and buffering layer for this requirement. EventBridge can publish orders.checkout events to a queue, and workers can consume them at a controlled rate even when the payment API is unavailable. This decouples event ingestion from downstream processing, absorbs bursts, and preserves events until the outage ends. A DLQ provides a safe landing zone for messages that continue to fail after retries so they are not silently dropped.

Increase the Lambda timeout so each invocation can wait longer for the payment API.Wrong answer — click to see why

Why this is wrong here

Increasing Lambda timeout does not address the root cause of downstream payment API timeouts; it only makes the Lambda wait longer, potentially exacerbating backpressure and event aging without improving resilience.

★ When this WOULD be the correct answer

This option would be correct if the question were about a Lambda function that fails due to a slow but eventually successful downstream API, and the goal is to avoid premature timeouts without changing the architecture.

Why candidates choose this

Candidates may think that giving the Lambda more time will allow it to succeed eventually, overlooking that the downstream API is failing and that waiting longer does not prevent event loss or backpressure.

Switch the target to a Lambda function with reserved concurrency of zero during outages.Wrong answer — click to see why

Why this is wrong here

Setting reserved concurrency to zero during outages would stop all invocations, causing all events to be lost or retried until they age out, rather than improving resilience or preserving events.

★ When this WOULD be the correct answer

This option would be correct in a scenario where you need to temporarily throttle or stop processing from a specific event source to protect a downstream system from overload, while using a DLQ or retry mechanism to preserve events for later processing.

Why candidates choose this

Candidates may think that reducing concurrency can prevent overload, but setting it to zero halts all processing, which contradicts the goal of preserving events during outages.

Replace EventBridge with CloudWatch Logs subscriptions so the consumer can poll the log stream later.Wrong answer — click to see why

Why this is wrong here

CloudWatch Logs subscriptions deliver log data to a consumer in near-real-time but do not provide a durable buffer or retry mechanism for downstream failures; events would still be lost if the consumer is unavailable, and there is no built-in DLQ for poison messages.

★ When this WOULD be the correct answer

This option would be correct if the requirement was to archive all events for long-term storage and allow a consumer to process them on its own schedule, with no need for real-time delivery or automatic retries during outages.

Why candidates choose this

Candidates may think that using CloudWatch Logs provides a persistent log that can be replayed later, overlooking that EventBridge already offers retries and a DLQ-like mechanism, and that log subscriptions do not buffer events during consumer downtime.

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 assume increasing timeouts or concurrency adjustments can fix backpressure issues, but they fail to recognize that decoupling with a durable queue is the only way to preserve events during extended downstream outages without losing them to retry expiration.

Trap categories for this question

  • Scenario analysis trap

    CloudWatch Logs subscriptions are not a durable application messaging pattern and are not a substitute for queue-based buffering in this scenario.

Detailed technical explanation

How to think about this question

Under the hood, EventBridge uses a synchronous invocation model for Lambda targets, meaning if the Lambda function times out or throttles, EventBridge retries the delivery up to its maximum retry policy (default 24 hours) before discarding the event. By inserting an SQS queue as an asynchronous buffer, you decouple the retry logic from EventBridge’s limited window, allowing workers to process events at their own pace with SQS’s 14-day retention and per-message visibility timeout. The DLQ acts as a safety net for messages that exceed the maximum receives (default 3), ensuring no single failing event blocks the queue 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 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.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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 — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Put an Amazon SQS queue between EventBridge and the consumer, and have workers drain the queue with a DLQ for poison messages. — Option B is correct because introducing an SQS queue between EventBridge and the consumer decouples the event delivery from the downstream payment API. During outages, events are stored durably in SQS and can be processed later without being lost. A Dead Letter Queue (DLQ) captures events that fail repeatedly, preventing poison messages from blocking the queue and ensuring no events age out due to retry exhaustion.

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 →

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.