MENU
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
Suggested Answer: C
Get Premium ARC-101 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
JE
Jessenia
11 months ago
A could work, but it might complicate things with all that business logic.
ME
Melvin
11 months ago
Wait, can Change Data Capture really handle all updates? Sounds too good to be true!
DE
Deandrea
12 months ago
Not sure about D, seems a bit overkill for this scenario.
JA
Jacob
12 months ago
Totally agree with B! External IDs are super helpful.
MI
Ming
1 year ago
I think B and C are solid choices for this integration.
RO
Ronnie
1 year ago
Designing an MDM solution sounds like a solid approach, especially for managing unique identifiers. I think option D could be a good choice too.
RE
Rebbeca
1 year ago
I think caching external IDs in middleware could work, but it seems like it might add complexity. Option A feels risky.
NG
Ngoc
1 year ago
I'm a bit unsure about Change Data Capture. I think it can help with real-time updates, but I can't recall all the details.
JO
Jolanda
1 year ago
I remember we discussed using External ID fields in Salesforce for mapping records, so option B sounds familiar.
JA
Jacinta
1 year ago
Caching the external IDs at the middleware layer and designing the business logic to handle the updates sounds like a good approach. That way we can decouple the systems a bit.
CY
Cyndy
1 year ago
I'm a bit confused by the different systems and how they all fit together. I'll need to diagram this out to really understand the data flows.
DO
Dorothy
1 year ago
Okay, I think the key here is to store the external IDs in Salesforce and use those to update the other systems. That way we have a central place to manage the mapping.
SI
Simona
1 year ago
This seems like a tricky integration problem. I'll need to carefully consider the different systems and how to best map the unique identifiers.
DO
Domitila
1 year ago
Using Change Data Capture could be a nice way to automatically propagate changes, but I'm not sure if that would work across all the different systems. I'll need to research that option further.
TH
Thea
1 year ago
I think I've got this one! Based on the requirement to make the "regulatory record" option visible in retention labels, I'm going to go with option C and run the Sec-RegulacoryComplianceUI cmdlet. That seems like the most direct way to enable that functionality in the admin interface.
AU
Audry
1 year 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.
LO
Lonny
1 year ago
An MDM solution could definitely help with complex integrations, but let's start with simpler solutions first.
DO
Dominque
1 year ago
D) Design an MDM solution that maps external ID's to the Salesforce record ID.
BU
Buck
1 year ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
WI
Willow
1 year ago
C) Use Change Data Capture to update downstream systems accordingly when a record changes.
SO
Sommer
1 year ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
ST
Steffanie
2 years 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.
OL
Olen
1 year 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.
EL
Elizabeth
1 year ago
B) Store unique identifiers in an External ID field in Salesforce and use this to update the proper records across systems.
LI
Lilli
1 year ago
A) Locally cache external ID'S at the middleware layer and design business logic to map updates between systems.
GO
Goldie
2 years ago
If only there was a magic button that said 'Sync All the Things' - that would make this integration a breeze!
CH
Chi
2 years ago
B is definitely the way to go! Storing the external IDs in Salesforce makes it easy to keep everything in sync.
MA
Maryann
1 year ago
Designing an MDM solution to map external IDs to Salesforce record IDs seems like a robust approach.
AV
Avery
1 year ago
Locally caching external IDs at the middleware layer could also be a good option for mapping updates.
VI
Vilma
1 year ago
I agree, using External ID fields in Salesforce simplifies the integration process.
CO
Corinne
1 year ago
B is definitely the way to go! Storing the external IDs in Salesforce makes it easy to keep everything in sync.
BE
Belen
2 years 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.
FR
Francoise
2 years ago
I agree with Francoisebie. Option B seems like a practical solution for keeping data synchronized.
BO
Bobbie
2 years ago
I think option B makes sense because it's easier to update records across systems using External ID field.