SAP-C02 Practice Question 65: Event Archive Replay Consumer Defect
AWS Certified Solutions Architect – Professional (SAP-C02) · Test 7 · question 5 of 10
An order platform publishes events to a custom Amazon EventBridge event bus. Six teams consume the events through their own rules and event patterns. When the bus was created, the company also created an archive that keeps all events for 30 days. A defect in the billing team's Lambda function produced wrong invoices from events that arrived over the last two days. The billing team has now fixed the function, and it must reprocess exactly those two days of events. The producer teams must not change anything, and the other five consumers must not receive the events a second time.
What should the solutions architect recommend?
Show answer and explanation
Answer:
In EventBridge, *"you can create an archive of events so that you can easily replay, or resend them to the event bus that originally received them, at a later time"*, for example *"to recover from errors."* When you start a replay you specify *"the time frame from which to select events to replay"* and, optionally, *"specific rules on the event bus to which EventBridge should replay the selected events."* Restricting the replay to the billing rule means the other five consumers do not see the events again, and nothing changes for the producers (option C). Replays add a replay-name field so that replayed events are identifiable and are not archived again.
- A is wrong because it makes the producer teams do work the requirements forbid, and it would deliver the events to all six consumers again. - B is wrong because a dead-letter queue contains only the events that failed delivery. The faulty invoices came from events that were processed successfully. - D is wrong because CloudTrail does not capture the event payload in a form that can be resent, and re-publishing would again reach all consumers.
Reference: Archiving and replaying events in Amazon EventBridge