Universal Containers (UC) has three systems: Salesforce, a cloud -based ERP system, and an on -premise Order Management System (OMS). An architect has been tasked with creating a solution that uses Salesforce as the system of record for Leads and the OMS as the system of record for Account and Contacts. UC wants Accounts and Contacts to be able to maintain their names in each system (i.e., "John Doe" in the OMS and "Johnny Doe" in Salesforce), but wants to have a consolidated data store which links referenced records across the systems. What approach should an architect suggest so the requirements are met?
A.
Have Salesforce poll the OMS nightly and bring in the desired Accounts and Contacts.
B.
Implement an integration tool to send OMS Accounts and Contacts to Salesforce.
C.
Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
D.
Use the Streaming API to send Account and Contact data from Salesforce to the OMS.
C.
Implement a Master Data Management strategy to reconcile Leads, Accounts, and Contacts.
Explanation:
Option C ("Implement a Master Data Management strategy") aligns perfectly with the given requirements. MDM addresses conflicting data definitions across systems, allowing consolidation of records into a consistent view, reconciling naming differences, and maintaining record cross-referencing efficiently. It provides a structured, robust framework ideal for scenarios involving multiple sources of truth, ensuring ongoing data synchronization integrity without the complexity or brittleness of frequent polling (A) or simplistic integration (B, D).