SF-Data-Arch Master Data Management Practice Question
A data architect is designing a master data management solution where customer records from Salesforce and a legacy system must be merged into a single golden record. The legacy system uses a customer ID that is a 10-digit number, while Salesforce uses a 15-character ID. The architect needs to create a unique cross-system identifier. Which approach best ensures uniqueness and traceability?
⚠ Common exam trap
The trap here is assuming that a single system's native ID can serve as a universal identifier, ignoring the need for cross-system uniqueness and traceability.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a composite key consisting of the source system code and the native ID, stored in an external ID field
A composite key of source system code and native ID provides a globally unique identifier that also indicates the record's origin. This is essential for master data management, as it allows the organization to trace data back to its source and perform accurate merges. It also supports upsert operations in Salesforce via an external ID field.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Salesforce's 15-character ID as the single identifier for all systems
Why it's wrong here
Salesforce IDs are unique within Salesforce but not across external systems. Using them as the sole identifier would cause collisions when integrating with the legacy system, which has its own ID space. Additionally, the legacy system may not be able to store or process Salesforce's case-sensitive 15-character ID.
- ✓
Use a composite key consisting of the source system code and the native ID, stored in an external ID field
Why this is correct
A composite key combining the source system code and the native ID ensures global uniqueness and traceability. Storing it in an external ID field allows Salesforce to reference the legacy record and perform upserts. This approach is scalable and avoids collisions, as each system's IDs are prefixed with a unique code.
- ✗
Use the customer's email address as the unique identifier
Why it's wrong here
Email addresses are not guaranteed to be unique; customers may share emails, or the same customer may have multiple emails. Using email as the primary identifier can lead to duplicate records and data quality issues. It also lacks a system-specific component for traceability.
- ✗
Generate a random UUID for each customer and store it in a custom field
Why it's wrong here
While UUIDs are unique, they lack traceability to the source system. Without a source system reference, it becomes difficult to trace back to the original record for auditing or reconciliation. Also, generating and maintaining UUIDs requires additional logic and may not be supported natively in all systems.
About these practice questions
One of 222 original SF-Data-Arch practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.