SF-Data-Arch Master Data Management Practice Question
A Salesforce data architect at a global manufacturer is defining the master data domain for 'Customer'. The company has separate business units that each maintain their own customer records. The architect must ensure that a single, authoritative Customer record exists and is referenced by all transactional systems. Which approach best achieves this?
⚠ Common exam trap
The trap here is assuming that duplicate prevention or real-time virtualization alone creates a master data domain, when a golden record and survivorship are essential.
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
✓
Define a master data domain with a golden record, survivorship rules, and a data stewardship process.
A master data domain is defined by a golden record, survivorship rules, and data stewardship. The golden record is the single authoritative version of a Customer, and survivorship rules determine which source system's data prevails when attributes conflict. Data stewardship ensures ongoing quality. This combination ensures all transactional systems reference the same authoritative Customer record, which is the goal.
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 Connect to virtualize customer data from each business unit system in real time.
Why it's wrong here
Salesforce Connect provides real-time access to external data but does not create a master record or resolve conflicts. It leaves data in source systems, so no single authoritative record exists. It also may not be suitable for high-volume transactional access. It does not fulfill the master data requirement.
- ✗
Create a single Account record type and enforce a unique external ID on the Account object.
Why it's wrong here
A unique external ID prevents duplicate Account records but does not by itself establish an authoritative master record or resolve conflicts from multiple business units. It also does not define survivorship rules or data stewardship processes. Uniqueness alone is insufficient for a master data domain.
- ✗
Implement Salesforce Duplicate Management with matching rules and duplicate rules.
Why it's wrong here
Duplicate Management helps prevent and manage duplicates within Salesforce, but it does not create a golden record or resolve cross-system conflicts. It is a data quality tool, not a master data management solution. It does not provide the authoritative record required across business units.
- ✓
Define a master data domain with a golden record, survivorship rules, and a data stewardship process.
Why this is correct
A master data domain requires a golden record that is the single source of truth, survivorship rules to determine which source wins in conflicts, and stewardship to maintain quality. This ensures all transactional systems reference the authoritative Customer record. It directly addresses the need for a single, authoritative record.
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.