INTEGRATION-ARCHITECTURE-DESIGNER practice question 2 of 25

An Integration Developer is developing an HR synchronization app for a client. The app synchronizes Salesforce record data changes with an HR system that's external to Salesforce. What should the integration architect recommend to ensure notifications are stored for up to three days if data replication fails?

Full set: 106 questions

Domain Design a Security Solution

Answer options
A: Change Data Capture Correct answer
B: Generic Events
C: Platform Events
D: Callouts
Correct Answer:
A. Change Data Capture
Explanation

Change Data Capture (CDC) is the ideal solution for this scenario. It is specifically designed to publish events for changes in Salesforce records (creations, updates, deletes, and undeletes) to facilitate data synchronization with external systems. Crucially, CDC events are retained on the event bus for up to 72 hours (three days). This built-in durability ensures that if the external HR system is down or the integration fails, the change notifications are preserved and can be replayed once the connection is restored, directly meeting the client's requirement.

Why Incorrect

B. Generic Events: This is not a standard Salesforce feature. If it refers to a custom Platform Event, its retention is typically 24 hours unless configured as high-volume, making it less suitable than the purpose-built CDC.
C. Platform Events: Standard-volume Platform Events are only retained for 24 hours. While high-volume Platform Events offer 72-hour retention, they require custom development (e.g., Apex triggers) to publish events upon record changes, whereas CDC provides this functionality out-of-the-box.
D. Callouts: Callouts are direct API requests without an inherent message queue or retention mechanism. If a callout fails, the transaction is lost unless a complex custom retry and storage solution is built.

References

1. Salesforce Developer Documentation, Change Data Capture Developer Guide, "Change Event Message Durability": "Change Data Capture provides a durable event stream. Change events are stored for up to three days (72 hours). You can retrieve stored events from the event bus." This directly supports the 3-day storage requirement.

2. Salesforce Architects, Architect's Guide to Event-Driven Architecture with Salesforce, "Data Synchronization" section: This guide positions Change Data Capture as the primary pattern for data synchronization use cases, stating, "Change Data Capture is the recommended solution for Salesforce data synchronization." It contrasts this with Platform Events, which are for more general business process notifications.

3. Salesforce Developer Documentation, Platform Events Developer Guide, "Platform Event Message Durability": "For standard-volume events, the retention is 24 hours. For high-volume events, the retention is 72 hours." This highlights that only a specific type of Platform Event meets the retention requirement, while CDC meets it by default for its intended purpose.

Scroll to Top