Salesforce Certified Platform Data Architect free question 6 / 10 · Domain 3: Salesforce Data Management
A Change Data Capture subscriber app was down for five days for maintenance. When it restarts, you do not want to miss the changes made in the meantime. Which statement matches "Change Event Storage and Delivery" in the Change Data Capture Developer Guide (Spring '23)?
- Events are retained for three days, so a Replay ID reaches back three days; reconcile the rest by a full comparison
- When the app restarts, Salesforce recreates the missed changes as new events
- Replay IDs are reassigned when you resubscribe, so after restarting you can only receive from the latest
- Replay from the last processed Replay ID and you receive the five days of change events that were missed
Show the answer and explanation
Answer: A
Why this is correct
Change Event Storage and Delivery says change events are stored temporarily and that subscribers can retrieve them within the retention window. Change event messages are stored in the event bus for three days, and the ReplayId of each message lets you re-read the stream after a given event. Events are stored in the order they were committed in Salesforce and delivered to subscribers in Replay ID order. If you are down for more than three days, part of the period cannot be replayed, so reconcile the copy with a full comparison.
Why the other options are wrong
"Replay from the last processed Replay ID and you receive the five days of change events that were missed" … The guide says change event messages are stored in the event bus for three days. Anything older than that cannot be re-read with a Replay ID after being down for five days.
"When the app restarts, Salesforce recreates the missed changes as new events" … The guide does not describe Salesforce recreating past change events when a subscription restarts.
"Replay IDs are reassigned when you resubscribe, so after restarting you can only receive from the latest" … The guide says a Replay ID represents an event in the stream and can be used to re-read the stream after a given point.
Why this matters for design
In an event-based sync there is a limit to how long the receiving side may be stopped. Prepare in advance the procedure for a full reconciliation when that limit is exceeded.