Data CloudIntermediatedmodata-modelmappingharmonization
Explain Data Model Objects vs standard CRM objects in architecture
Real World Scenario
Your integration team asks why customer data lands in Individual and Contact Point Email DMOs instead of directly updating Salesforce Contact records.
Expected Answer
• DMOs are canonical schema in Data Cloud independent of any single source system shape
• Ingestion lands raw data in DLOs; mapping transforms to DMOs with standardized fields
• CRM objects remain system-of-record for operational workflows; Data Cloud is analytical/profile layer
• Bi-directional sync requires explicit activation or Data Actions—not automatic DMO-to-Contact write
• DMO design enables multi-source unification impossible in single Contact object model
• Governance: DMO field additions need enterprise data council approval
• Lineage metadata tracks which source contributed each attribute value
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Use this approach when volume, complexity, or compliance demands it. DMOs are canonical schema in Data Cloud independent of any single source system shape. Avoid it when a simpler declarative solution works. Treat DMOs as the enterprise customer schema, not a staging area for CRM. Balance speed of delivery with maintainability.
Architect Perspective
Treat DMOs as the enterprise customer schema, not a staging area for CRM. Confusion here causes teams to expect real-time Contact updates from every ingested event.