mediummultiple choiceObjective-mapped

Your order-processing system uses EventBridge rules to send events to a Lambda function that updates order status. Over the last week, some events fail with a transient database timeout, and the Lambda retries intermittently but then the events are lost (no alerts after failures). You want at-least-once processing, bounded retries, and a way to inspect unprocessable events for later reprocessing.

Which architecture change best meets these requirements?

Question 1mediummultiple choice
Full question →

Your order-processing system uses EventBridge rules to send events to a Lambda function that updates order status. Over the last week, some events fail with a transient database timeout, and the Lambda retries intermittently but then the events are lost (no alerts after failures). You want at-least-once processing, bounded retries, and a way to inspect unprocessable events for later reprocessing.

Which architecture change best meets these requirements?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Send EventBridge events to an SQS queue, configure a redrive policy to move messages to a dead-letter queue (DLQ) after a defined receive count, and make the Lambda processing idempotent.

EventBridge-to-SQS provides buffering and decoupling; SQS redrive with a DLQ bounds retries and preserves failed events for analysis and replay.

B

Distractor review

Invoke Lambda directly from EventBridge in asynchronous mode, and increase the Lambda timeout to reduce failures.

Direct asynchronous invocation lacks a DLQ-style retention mechanism for failed events and retries can be unpredictable.

C

Distractor review

Use SNS topics with Lambda subscriptions, but remove all retry and DLQ configuration to minimize duplicate events.

Removing retries and DLQ leads to message loss and provides no systematic way to capture unprocessable events.

D

Distractor review

Store failed events only in CloudWatch logs, and have operators manually copy log entries back into the database for reprocessing.

Logs are not a reliable data store for event replay and operationally burdens incident response while risking inconsistencies.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Send EventBridge events to an SQS queue, configure a redrive policy to move messages to a dead-letter queue (DLQ) after a defined receive count, and make the Lambda processing idempotent. — The best solution is to buffer events with SQS and explicitly manage failure handling. Routing EventBridge to SQS decouples the producer from the consumer and supports at-least-once delivery. Configuring an SQS redrive policy moves messages to a DLQ after a defined receive count, ensuring bounded retries and preserving failed events for later investigation or replay. Idempotent processing in Lambda prevents harmful effects from duplicates due to at-least-once delivery, satisfying correctness during transient failures. Why others are wrong: Direct EventBridge-to-Lambda asynchronous invocation may retry, but it does not reliably provide a DLQ-style mechanism for capturing all failed events for later replay. SNS can fan out, but removing retries and DLQs contradicts the requirement to preserve unprocessable events. Using CloudWatch logs as a replay source is unreliable and does not guarantee data fidelity or automated recovery workflows.

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

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.