DATA-ARCHITECT practice question 32 of 35

NTO has multiple systems across its enterprise landscape including salesforce, with disparate version the customer records. In salesforce, the…

Full set: 257 questions
NTO has multiple systems across its enterprise landscape including salesforce, with disparate version the customer records. In salesforce, the customer is represented by the contact object. NTO utilizes an MDM solution with these attributes: 1. The MDM solution keeps track of customer master with a master key. 2. The master key is a map to the record ID’s from each external system that customer data is stored within. 3. The MDM solution provides de-duplication features, so it acts as the single source of truth. How should a data architect implement the storage of master key within salesforce?
Answer options
A: Store the master key in Heroku postgres and use Heroku connect for synchronization.
B: Create a custom object to store the master key with a lookup field to contact.
C: Create an external object to store the master key with a lookup field to contact.
D: Store the master key on the contact object as an external ID (Field for referential imports) Correct answer
Correct Answer:
D. Store the master key on the contact object as an external ID (Field for referential imports)
Explanation

The most efficient and standard method to store a unique identifier from an external system, like an MDM master key, is by using a custom field on the Salesforce object marked as an "External ID". This field type is specifically designed for this purpose. It is indexed by Salesforce, which significantly improves performance for data operations, particularly for "upsert" calls from the integration, which use the external ID to find and update or create the correct record. This approach avoids the overhead of extra objects or platforms.

Why Incorrect

A. Using Heroku is overly complex and expensive for storing a single key, introducing unnecessary synchronization layers.
B. A custom object adds an extra record and join for what is a one-to-one attribute of the Contact, which is inefficient.
C. An external object is used to access data stored outside of Salesforce, not for storing an external key inside Salesforce.

References

1. Salesforce Developer Documentation, Custom Field Types. "External ID: A custom field that has the “External ID” attribute, meaning that it contains unique record identifiers from a system outside of Salesforce."

2. Salesforce Architects, Architect's Guide to Record-Level Data, "Record Identifiers" section. This guide discusses using External IDs as a best practice for integrating with external systems and maintaining a stable key for data synchronization.

3. Salesforce Integration Patterns and Practices, Remote Process Invocation—Request and Reply, Page 11. The document discusses using External IDs to simplify integration logic by allowing upsert operations based on a stable identifier from the remote system.

Scroll to Top