What should a consultant recommend to meet this requirement?

Cloud Kicks’ (CK) VP of technology wants to start using Sales Cloud for all of the sales team’s automation. CK migrated 70 million records from a legacy database to the data warehouse that will be synced

with Sales Cloud. CK wants to search and cross-reference records with the original source database.

What should a consultant recommend to meet this requirement?
A . Use the standard External ID field and map this to the source record ID value.
B . Use a custom field named External ID and map this to the Sales Cloud record value.
C . Use a custom External ID field and map this to the source record ID value.

Answer: C

Explanation:

To facilitate record referencing and synchronization between Sales Cloud and an external database, the best practice is to use a custom External ID field. This field can be mapped directly to the unique record ID from the source database. External ID fields in Salesforce are specifically designed for integrating with external systems, allowing efficient data cross-referencing and deduplication. Using a custom External ID field ensures that the migrated records maintain a unique identifier that matches the original source, simplifying future synchronization and data management tasks. This setup is especially useful when dealing with large volumes of data, as in the case of Cloud Kicks, which has migrated 70 million records. This method is preferable over a standard External ID, as it offers flexibility in defining the exact field and data type to meet Cloud Kicks’ specific requirements.

Reference: Salesforce documentation on External ID fields and data management strategies supports the use of custom External ID fields for large-scale data integrations.