Salesforce ArchitectureArchitect (Hardest)mdmmaster-datadata-governance
Design Master Data Management strategy with Salesforce
Real World Scenario
Customer data duplicated across Salesforce SAP and marketing tools with no golden record authority.
Expected Answer
• Define golden record system per domain: CRM for sales relationship, MDM for legal entity
• Salesforce as MDM hub vs contributor depends on enterprise architecture
• Data Cloud identity resolution as modern alternative to traditional MDM for profiles
• Stewardship workflows for merge split and attribute override
• Data quality rules at ingestion with quarantine patterns
• Sync patterns: bi-directional with survivorship not blind overwrite
• Executive data council owning definitions and conflict resolution SLAs
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Define golden record system per domain: CRM for sales relationship, MDM for legal entity. Salesforce as MDM hub vs contributor depends on enterprise architecture. Pick based on your integration pattern and team capability. MDM fails from politics not technology—architect attribute authority matrix with business sign-off. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
MDM fails from politics not technology—architect attribute authority matrix with business sign-off.