Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam ARC-101 Topic 9 Question 44 Discussion

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

Universal Containers (UC) uses Salesforce to track the following customer data:

1. Leads,

2. Contacts

3. Accounts

4. Cases

Salesforce is considered to be the system of record for the customer. In addition to Salesforce, customer data exists in an Enterprise Resource Planning (ERP) system, ticketing system, and enterprise data lake. Each of these additional systems have their own unique identifier. UC plans on using middleware to integrate Salesforce with the external systems.

UC has a requirement to update the proper external system with record changes in Salesforce and vice versa.

Which two solutions should an Integration Architect recommend to handle this requirement?

Choose 2 answers

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Audry
1 months ago
An MDM solution, huh? That could be overkill for this use case, but it might be worth looking into if the integration gets really complex.
upvoted 0 times
Lonny
18 hours ago
An MDM solution could definitely help with complex integrations, but let's start with simpler solutions first.
upvoted 0 times
...
Dominque
17 days ago
D) Design an MDM solution that maps external ID's to the Salesforce record ID.
upvoted 0 times
...
Buck
19 days ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
upvoted 0 times
...
Willow
26 days ago
C) Use Change Data Capture to update downstream systems accordingly when a record changes.
upvoted 0 times
...
Sommer
1 months ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
upvoted 0 times
...
...
Steffanie
2 months ago
Hmm, I'm not sure about caching the external IDs at the middleware layer. Sounds like it could get messy if we're not careful.
upvoted 0 times
Olen
6 days ago
Hmm, I'm not sure about caching the external IDs at the middleware layer. Sounds like it could get messy if we're not careful.
upvoted 0 times
...
Elizabeth
7 days ago
B) Store unique identifiers in an External ID field in Salesforce and use this to update the proper records across systems.
upvoted 0 times
...
Lilli
8 days ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
upvoted 0 times
...
...
Goldie
2 months ago
If only there was a magic button that said 'Sync All the Things' - that would make this integration a breeze!
upvoted 0 times
...
Chi
2 months ago
B is definitely the way to go! Storing the external IDs in Salesforce makes it easy to keep everything in sync.
upvoted 0 times
Maryann
3 days ago
Designing an MDM solution to map external IDs to Salesforce record IDs seems like a robust approach.
upvoted 0 times
...
Avery
5 days ago
Locally caching external IDs at the middleware layer could also be a good option for mapping updates.
upvoted 0 times
...
Vilma
1 months ago
I agree, using External ID fields in Salesforce simplifies the integration process.
upvoted 0 times
...
Corinne
1 months ago
B is definitely the way to go! Storing the external IDs in Salesforce makes it easy to keep everything in sync.
upvoted 0 times
...
...
Belen
2 months ago
I'm not sure about option B. I think option D might be more efficient in mapping external ID's to Salesforce record ID.
upvoted 0 times
...
Francoise
2 months ago
I agree with Francoisebie. Option B seems like a practical solution for keeping data synchronized.
upvoted 0 times
...
Bobbie
2 months ago
I think option B makes sense because it's easier to update records across systems using External ID field.
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