Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam ARC-101 Topic 2 Question 29 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 29
Topic #: 2
[All ARC-101 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Ivette
8 days ago
I'm not sure. Would Generic Events also be a good option for storing notifications in case of data replication failure?
upvoted 0 times
...
Osvaldo
9 days ago
I agree with Orville. Platform Events can store notifications for up to three days if data replication fails.
upvoted 0 times
...
Orville
10 days ago
I think the integration architect should recommend Platform Events.
upvoted 0 times
...
Slyvia
11 days ago
I'm not sure. Maybe Change Data Capture could also be a good option for this scenario.
upvoted 0 times
...
Mireya
13 days ago
I agree with Laurel. Platform Events can store notifications for up to three days if data replication fails.
upvoted 0 times
...
Nancey
13 days ago
I'm leaning towards Platform Events too. Seems like the most robust option to ensure we don't lose any important data.
upvoted 0 times
...
Justine
16 days ago
Hmm, Platform Events sounds like the way to go here. Storing notifications for up to three days in case of data replication failures is exactly what they're designed for.
upvoted 0 times
...
Laurel
19 days ago
I think the integration architect should recommend Platform Events.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77