Salesforce Decode
Salesforcedecode
Back to questions
IntegrationArchitect (Hardest)mdmsyncmaster-data

Design bi-directional sync between Salesforce and external MDM

Real World Scenario

Customer golden record lives in Informatica MDM but sales reps edit Account addresses in Salesforce. Conflicts arise weekly.

Expected Answer

• Define system of record per attribute: MDM for legal entity name, SF for sales owner • Survivorship rules applied in MDM with Salesforce as contributor source • Conflict queue for human resolution when both systems update same field • Last-modified-wins only where business accepts; otherwise MDM authority • Sync frequency: near-real-time for critical fields, batch for enrichments • External ID on Account linking MDM golden record key • Data stewardship workflow with SLA for conflict resolution

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Define system of record per attribute: MDM for legal entity name, SF for sales owner. Survivorship rules applied in MDM with Salesforce as contributor source. Pick based on your integration pattern and team capability. Bi-directional sync without survivorship rules guarantees conflict—architect attribute-level authority matrix first. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Bi-directional sync without survivorship rules guarantees conflict—architect attribute-level authority matrix first.