Discuss Salesforce Plat-Arch-204 Exam Topic 5 Question 6

Universal Containers (UC) has a legacy homegrown application that stores customer data. Sales representatives edit contact records in Salesforce. UC requirements: 1. Salesforce updates should update the homegrown application. 2. Synchronization should be event-driven. 3. Integration should be asynchronous. Which option should an architect recommend?

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

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

Suggested Answer: A

For a requirement focused on synchronizing record updates from Salesforce to an external system in an event-driven and asynchronous manner, Change Data Capture (CDC) is the architecturally preferred solution over custom Platform Events.

CDC is designed specifically for data replication and synchronization. It automatically publishes change events for Salesforce records (Create, Update, Delete, and Undelete) to the event bus. Unlike Platform Events, which require manual publishing via Apex triggers or Flows, CDC is a low-code feature that requires only a simple activation for the Contact object in Setup. The external homegrown application can then act as a CometD subscriber, listening to the specialized /data/ContactChangeEvent channel to receive near real-time updates without the need for constant polling. Furthermore, CDC provides ordered, replayable events and an extended 72-hour retention window, ensuring that the homegrown application can recover missed updates using a Replay ID if it momentarily loses connection. This native broadcasting capability ensures data integrity across systems while breaking the tight coupling between Salesforce and the legacy application.

Get Premium Plat-Arch-204 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

25 comments · newest first

Lizette 6 months ago

But option B offers more flexibility with event handling. It could be more scalable.

Sabrina 6 months ago

Option A allows for real-time updates. That's crucial for our needs.

Salena 6 months ago

I prefer option B. Platform Events are great for custom event messaging.

Felice 6 months ago

I think option A is better. Change Data Capture is efficient for tracking changes.

Lisbeth 6 months ago

Totally agree with A), it fits the requirements perfectly!

Pilar 7 months ago

Wait, can it really handle asynchronous updates like that?

Mitsue 7 months ago

Change Data Capture is great for tracking changes!

Alyce 7 months ago

I think B) is better for custom event handling.

Ilene 7 months ago

A) sounds solid for real-time updates!

Christoper 7 months ago

Platform Events all the way! Gotta love that event-driven architecture.

Huey 8 months ago

Hmm, I'm not sure. Change Data Capture might be a simpler solution. Depends on the specific requirements.

Brock 8 months ago

I agree, Platform Events are the way to go. Asynchronous integration is key for this use case.

Soledad 8 months ago

Option B seems like the way to go. Platform Events are designed for this kind of event-driven integration.

Ming 8 months ago

I lean towards option B because it allows for custom event messages, but I wonder if it can keep up with the volume of changes we might see.

Quentin 9 months ago

I feel like I've seen a similar question before, and I think Change Data Capture was the answer. But I'm a bit confused about how it integrates with the homegrown app.

Arthur 9 months ago

I remember practicing with Platform Events, and they seem to fit the event-driven requirement well. But does it handle the asynchronous part effectively?

Desmond 9 months ago

I think option A sounds familiar, especially with Change Data Capture. It might be the right choice for tracking changes, but I'm not entirely sure how CometD works.

Eloisa 9 months ago

This is a tricky one. I'm not super familiar with the Salesforce integration features, so I'll need to do a bit of research on Change Data Capture and Platform Events to understand the pros and cons of each approach. I want to make sure I recommend the best solution.

Ernest 9 months ago

I'm leaning towards Option A. Leveraging Change Data Capture to track the Salesforce changes and then using a CometD subscriber on the homegrown app seems like a solid approach. I'll need to double-check the details, but this option feels more straightforward to implement.

Martina 10 months ago

Option B looks promising to me. Using Platform Events to publish custom event messages containing the Contact updates seems like a good way to achieve the event-driven and asynchronous requirements. I'll make sure to explain how that would work in my answer.

Janna 10 months ago

Hmm, I'm a bit confused. Both options mention using Salesforce features to track changes, but I'm not sure how the homegrown application would receive those updates asynchronously. I'll need to think this through carefully.

Kenia 10 months ago

This question seems straightforward - it's asking us to recommend the best option for integrating Salesforce with a legacy homegrown application. The key requirements are event-driven and asynchronous synchronization.

Teri 4 months ago

↳ replying to Kenia

Both options have their merits, but I lean towards A for real-time updates.

Anjelica 5 months ago

↳ replying to Kenia

I prefer option B. Platform Events seem more flexible for custom messages.

Lore 6 months ago

↳ replying to Kenia

I think option A is the way to go. Change Data Capture sounds perfect for tracking changes.

Salesforce Plat-Arch-204 Exam - Topic 5 Question 6 Discussion