DATA-ARCHITECT practice question 27 of 35

A large retail B2C customer wants to build a 360 view of its customer for its call center agents. The customer interaction is currently maintained in the following system: 1. Salesforce CRM 3. Customer Master Data management (MDM) 4. Contract Management system 5. Marketing solution What should a data architect recommend that would help upgrade uniquely identify customer across multiple systems:

Full set: 257 questions
Answer options
A: Store the salesforce id in all the solutions to identify the customer.
B: Create a custom object that will serve as a cross reference for the customer id.
C: Create a customer data base and use this id in all systems.
D: Create a custom field as external id to maintain the customer Id from the MDM solution. Correct answer
Correct Answer:
D. Create a custom field as external id to maintain the customer Id from the MDM solution.
Explanation

The presence of a Master Data Management (MDM) system indicates it is the authoritative source of truth for customer identity. The best practice for integrating systems with an MDM is to use the MDM's unique identifier as the common key. Creating a custom field in Salesforce, marking it as an "External ID," and storing the customer ID from the MDM system establishes a reliable foreign key relationship. This allows Salesforce to be a spoke in the MDM hub model, enabling consistent customer identification and facilitating a true 360-degree view across all connected systems.

Why Incorrect

A. This incorrectly positions Salesforce as the master system for customer identity, contradicting the role of the MDM and creating tight coupling.
B. A cross-reference object in Salesforce duplicates the primary function of the MDM system, adding unnecessary complexity and potential for data drift.
C. Creating another database adds a new system to manage, further fragmenting the data landscape instead of unifying it around the existing MDM.

References

1. Salesforce Help, "Custom Field Attributes." The documentation for the "External ID" attribute states it is used to "store a unique identifier from a system outside of Salesforce," which is precisely this use case.

2. Gartner, Magic Quadrant for Master Data Management Solutions, (e.g., 2021 report, ID G00742302). These reports define MDM's role as providing "a single, trusted view of a master data entity" to be "shared across an enterprise." This supports using the MDM ID as the primary cross-system identifier.

3. Salesforce Architects, "Sharing and Visibility Designer Exam Guide," under "System of Record," discusses patterns for identifying the authoritative source for a given data entity.

Scroll to Top