DOP-C02 Practice Question 59: EventBridge Archive Replay
AWS Certified DevOps Engineer – Professional (DOP-C02) · Test 6 · question 9 of 10
A team discovers that a bug in one of its event consumers caused every event matching a particular EventBridge rule to be processed incorrectly over the last six hours. The bug is now fixed, and the team needs to reprocess exactly those events, in their original content, through the corrected consumer. The producers that originally published the events cannot easily republish them on demand. The event bus already has archiving enabled.
What should the team do to reprocess the affected events?
Show answer and explanation
Answer:
An EventBridge archive stores a copy of every event that passes through the bus (or that matches an optional filter), together with the time it was received. A replay reads events out of that archive for a specified time range and resends them, with their original content and in their original order, to a chosen rule's targets, exactly what is needed to reprocess events a downstream bug mishandled, without touching the original producers at all.
Option A depends on producers being able and willing to resend historical events on demand, which the scenario says is not practical, and most producers have no mechanism to replay their own past output.
Option B is a misunderstanding of what a rule's dead-letter queue holds: it captures events that EventBridge failed to deliver to a target, not every event that matched the rule and was delivered but then mishandled downstream by a buggy consumer.
Option D confuses two different features: CloudTrail data events record the API calls made against a resource, not the EventBridge events themselves, and CloudTrail has no mechanism to replay recorded API activity back into an event bus.
Reference: Replaying archived events