ExamPark
Course menuDOP-C02

Exams / DOP-C02 / EventBridge rules and event-driven responses / Question 3

DOP-C02 practice question: EventBridge rules and event-driven responses (3 of 3)

Incident and Event Response A free question from our original DOP-C02 practice exam. Try it, then open the answer to see why each option is right or wrong.

Last verified against current AWS documentation ·How we write our questions

An insurance firm publishes ClaimSubmitted events to an EventBridge event bus. A rule sends each event to an AWS Lambda function that validates the claim and writes it to a claims database.

During a database maintenance window, the function returned errors for about 20 minutes, and some claims were lost after the retries ran out. The claims team needs failed claims to be retried for a time, and any event that still cannot be processed must be kept for later reprocessing.

The team wants a configuration change only, without changing the producer or the function's code.

Which change meets these requirements?

Choose one answer.

  1. A. Set the function's reserved concurrency to a higher number, so that more invocations can run at once and fewer events are dropped during a busy period.
  2. B. Wrap the handler in a try block that logs any database error and returns a success response, so that the invocation never counts as failed and is never retried.
  3. C. Configure the function's asynchronous invocation retry attempts and maximum event age, and add an Amazon SQS on-failure destination for events that still fail.
  4. D. Configure the rule's target with a retry policy for the maximum event age and retry count, and an Amazon SQS dead-letter queue that receives any event the rule cannot deliver.
Show the answer and explanation

Answer: C

Explanation

EventBridge invokes Lambda asynchronously, so once Lambda accepts an event, function errors are handled by Lambda's own retries, not by the rule's retry policy. Configuring the function's asynchronous retry settings and an SQS on-failure destination keeps every event that still fails. Rule-level dead-letter queues, reserved concurrency and swallowed errors leave the claims lost.

A Lambda on-failure destination compared with a dead-letter queue An event source such as SNS, EventBridge or S3 invokes a Lambda function asynchronously. When every retry fails, an on-failure destination SQS queue receives a record with the event, the response status code and the error payload. A dead-letter queue, shown for comparison, keeps only the event and a few attributes. Event source SNS, EventBridge, S3 async invoke Lambda function all retries fail SQS queue on-failure destination Dead-letter queue event only record: event, status, error payload
Lambda's own async retries handle the failures, and the SQS on-failure destination keeps every event that still fails.

Study

Keep practicing

Answer questions with a score at the end, or practice just this topic with the explanation after each one. No sign-up needed.

Take the free DOP-C02 practice examPractice EventBridge rules and event-driven responsesAll EventBridge rules and event-driven responses questions

Want more on EventBridge rules and event-driven responses? The 5 full-length practice sets have 13 more EventBridge rules and event-driven responses questions, 375 in all, none of them in the free exam. One payment of $14.99, no subscription. See the practice sets