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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce ARC-101 Exam - Topic 6 Question 70 Discussion

Actual exam question for Salesforce's ARC-101 exam
Question #: 70
Topic #: 6
[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: A

https://trailhead.salesforce.com/en/content/learn/modules/change-data-capture/understand-change-data-capture


by Maybelle at Jan 26, 2026, 06:39 PM

Limited Time Offer

25%

Off

Get Premium ARC-101 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Cordell
13 hours ago
Totally agree, queues are the way to go!
upvoted 0 times
...
Mabel
6 days ago
Use a message queue for reliable storage.
upvoted 0 times
...
Hermila
11 days ago
I'd suggest a combination of a message queue and a distributed cache. That way, you can handle the short-term storage and also scale up if needed.
upvoted 0 times
...
Trinidad
16 days ago
Haha, three days of notifications? Sounds like a recipe for a massive backlog. Better hope the client doesn't have too many data changes!
upvoted 0 times
...
Bette
21 days ago
Hmm, a message queue sounds like a good solution, but what if we need to scale it up in the future? Maybe a distributed caching solution would be better.
upvoted 0 times
...
Tarra
26 days ago
I'd recommend using a persistent message queue like Amazon SQS or RabbitMQ to handle the data replication failures.
upvoted 0 times
...
Gianna
1 month ago
Definitely go with a message queue to store the notifications for up to three days.
upvoted 0 times
...
Casey
1 month ago
Could it be that we need to set up a dead-letter queue? I think that was mentioned in a similar scenario we practiced.
upvoted 0 times
...
Elfriede
2 months ago
I feel like we discussed using a database or a temporary storage service for failed notifications, but I can't recall the specifics.
upvoted 0 times
...
Julianna
2 months ago
I remember a practice question about error handling in integrations. Maybe we should use a retry mechanism along with a persistent storage solution?
upvoted 0 times
...
Nada
2 months ago
I think we might need to implement a message queue to handle the notifications, but I'm not entirely sure how long they can be stored.
upvoted 0 times
...
Gail
3 months ago
I feel pretty confident about this one. I'd recommend using a Salesforce-native solution like Platform Events to capture the data changes, then have a process that stores those event notifications for up to 3 days in case the external system goes down. That way the data stays in Salesforce until it can be successfully synced.
upvoted 0 times
...
Cecily
3 months ago
Okay, this seems like it's getting into some more advanced Salesforce integration concepts. I'd probably want to review the documentation on asynchronous messaging patterns to make sure I understand the best way to handle potential data replication failures and maintain those notifications.
upvoted 0 times
...
Alaine
3 months ago
Hmm, not sure about that one. Outbound Messaging might work, but I'm wondering if there are other Salesforce tools like Platform Events or Change Data Capture that could be better suited for this use case. I'll need to research the options more.
upvoted 0 times
...
Mona
3 months ago
I think I'd start by looking at the Salesforce Outbound Messaging feature to set up notifications for data changes. That could help store the updates for a few days if the external system is down.
upvoted 0 times
...

Save Cancel