INTEGRATION-ARCHITECTURE-DESIGNER practice question 13 of 25

Sales representatives at Universal Containers (UC) use Salesforce Sales Cloud as their primary CRM. UC owns a legacy homegrown application that…

Full set: 106 questions

Domain Design an Integration Solution

Sales representatives at Universal Containers (UC) use Salesforce Sales Cloud as their primary CRM. UC owns a legacy homegrown application that stores a copy of customer dataas well. Sales representatives may edit or update Contact records in Salesforce if there is a change. Both Salesforce and the homegrown application should be kept synchronized for consistency. UC has these requirements: 1. When a Contact record in Salesforce is updated, the external homegrown application should be 2. The synchronization should be event driven. 3. The integration should be asynchronous. Which option should an architect recommend to satisfy the requirements?

Answer options
A:

A. Leverage Platform Events to publish a custom event message containing changes to the Contact object.

B:

B. Leverage Change Data Capture to track changes to the Contact object and write a CometD subscriber on the homegrown application.

Correct answer
C:

C. Write an Apex Trigger with the @future annotation.

D:

D. Use an ETL tool to keep Salesforce and the homegrown application in sync on a regular candence.

Correct Answer:
B. B. Leverage Change Data Capture to track changes to the Contact object and write a CometD subscriber on the homegrown application.
Explanation

Change Data Capture (CDC) is the most suitable solution as it is specifically designed for broadcasting record changes asynchronously and in an event-driven manner. When a Contact record is updated in Salesforce, CDC automatically publishes a change event containing details of the modification. The external homegrown application can then subscribe to this event stream using a CometD client to receive the updates in near real-time. This approach directly meets all requirements for event-driven, asynchronous synchronization with minimal custom implementation on the Salesforce side.

Why Incorrect

A. Platform Events would also work, but they require custom development (Apex trigger or Flow) to construct and publish the event, whereas CDC provides this functionality declaratively for record changes.
C. An Apex trigger with a @future callout creates a point-to-point integration. While asynchronous, this is less scalable and more tightly coupled than a publish-subscribe model like Change Data Capture.
D. An ETL tool operating on a "regular cadence" describes a scheduled batch process, which directly contradicts the requirement for an "event-driven" synchronization.

References

1. Salesforce Developer Documentation, Change Data Capture Developer Guide, "Change Data Capture Basics": "Change Data Capture is a streaming product on the Lightning Platform that enables you to efficiently integrate your Salesforce data with external systems. With Change Data Capture, you can receive changes of Salesforce records in real time and synchronize corresponding records in an external data store." This source confirms CDC is the purpose-built tool for real-time, event-driven data synchronization.

2. Salesforce Architects, "Architect's Guide to Event-Driven Architecture with Salesforce": In the section "Choosing the Right Eventing Solution," the guide positions Change Data Capture for "Record changes (create, update, delete, undelete)" and highlights its use for "Data replication." This directly aligns with the question's scenario of synchronizing Contact record updates.

3. Trailhead, Change Data Capture Basics, "Get Started with Change Data Capture": "Change Data Capture publishes events for changes in Salesforce records. ... Applications can subscribe to change events to... synchronize data with an external system." This reinforces that CDC is the standard mechanism for the required functionality.

Scroll to Top