Question 41
Choose 1
UC has multiple SF orgs that are distributed across regional branches. Each branch stores local customer data inside its org’s Account and Contact objects. This creates a scenario where UC is unable to view customers across all orgs. UC has an initiative to create a 360-degree view of the customer, as UC would like to see Account and Contact data from all orgs in one place. What should a data architect suggest to achieve this 360-degree view of the customer?
Correct answer:
A. Consolidate the data from each org into a centralized datastore
Explanation:
A centralized datastore allows UC to bring customer data from all regional Salesforce orgs into one system, enabling a single source of truth and consistent reporting. This is a common pattern called multi-org consolidation. By creating a hub (such as a data warehouse, MDM system, or Customer 360), UC can aggregate Account and Contact data, resolve duplicates, and maintain consistency across branches. This design provides scalability and avoids messy point-to-point integrations.
Why not the others?
B. Use Salesforce Connect’s cross-org adapter:
While Connect can surface data from other orgs virtually, it doesn’t consolidate or normalize the data. Performance suffers when querying millions of records across orgs, and features like cross-org deduplication or unified reporting aren’t possible. It’s useful for lightweight access, but not for a true 360-degree customer view.
C. Build a bidirectional integration between all orgs:
This creates a complex web of integrations where each org pushes and pulls data to every other org. Maintenance quickly becomes unmanageable as the number of orgs grows (n² problem). Data consistency issues are also likely, since real-time sync across multiple orgs often introduces race conditions and conflicts.
D. Use an ETL tool to migrate gap Accounts and Contacts into each org:
Copying missing data into every org creates duplication instead of unification. Each org will have slightly different versions of the same record, which increases data quality problems. ETL is better suited to feed a central system, not to spread data redundantly across all orgs.
Reference:
Salesforce Architect Guide: Multi-Org Strategy
A centralized datastore allows UC to bring customer data from all regional Salesforce orgs into one system, enabling a single source of truth and consistent reporting. This is a common pattern called multi-org consolidation. By creating a hub (such as a data warehouse, MDM system, or Customer 360), UC can aggregate Account and Contact data, resolve duplicates, and maintain consistency across branches. This design provides scalability and avoids messy point-to-point integrations.
Why not the others?
B. Use Salesforce Connect’s cross-org adapter:
While Connect can surface data from other orgs virtually, it doesn’t consolidate or normalize the data. Performance suffers when querying millions of records across orgs, and features like cross-org deduplication or unified reporting aren’t possible. It’s useful for lightweight access, but not for a true 360-degree customer view.
C. Build a bidirectional integration between all orgs:
This creates a complex web of integrations where each org pushes and pulls data to every other org. Maintenance quickly becomes unmanageable as the number of orgs grows (n² problem). Data consistency issues are also likely, since real-time sync across multiple orgs often introduces race conditions and conflicts.
D. Use an ETL tool to migrate gap Accounts and Contacts into each org:
Copying missing data into every org creates duplication instead of unification. Each org will have slightly different versions of the same record, which increases data quality problems. ETL is better suited to feed a central system, not to spread data redundantly across all orgs.
Reference:
Salesforce Architect Guide: Multi-Org Strategy
