SF-Data-Arch Data Governance Practice Question
An architect is designing a governance framework for Master Data Management (MDM). Which approach is best for ensuring 'Golden Record' consistency in Salesforce?
⚠ Common exam trap
Many candidates choose 'standard Salesforce duplicate rules' as the solution, forgetting that MDM requires a cross-system synchronization strategy, not just internal record matching within a single Salesforce org.
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
✓
Implementing an external MDM hub.
A Master Data Management strategy requires a 'Source of Truth' identification. By defining which system holds the primary record and using integration middleware to synchronize these records, the architect creates a consistent 'Golden Record'. This prevents data fragmentation where different systems maintain conflicting versions of the same customer, which is the core challenge MDM aims to solve.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Using Duplicate Rules to merge records.
Why it's wrong here
Salesforce duplicate rules are great for tactical cleanup but are not sufficient for enterprise MDM. They lack the logic to reconcile data across disparate external systems. Relying solely on platform tools for MDM ignores the need for cross-system orchestration and centralized data stewardship required for a true Golden Record.
- ✓
Implementing an external MDM hub.
Why this is correct
An external hub acts as the central authority for master data. It validates, cleanses, and synchronizes the 'Golden Record' across all connected systems, including Salesforce. This approach is superior for enterprise environments where data exists across multiple platforms and needs a single, unified source of truth to maintain data integrity.
- ✗
Creating custom formula fields.
Why it's wrong here
Formula fields are for displaying data, not for master record reconciliation. They do not store data, nor do they provide the synchronization logic necessary to integrate with other business systems. Using formula fields for MDM is a fundamental misunderstanding of the platform's capabilities and will result in significant data inconsistencies.
- ✗
Enabling Person Accounts for all users.
Why it's wrong here
Person Accounts are a data model choice for B2C organizations. Enabling them does not resolve conflicts between systems or establish a 'Golden Record'. It is a structural platform configuration that has nothing to do with the governance or logic required for effective Master Data Management across the enterprise architecture.
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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.