Harmonization and Unification17% of the exam
Data mapping, DMOs, relationships and data graphs
How to model data in Data 360: mapping rules and automapping, required party mappings, key qualifiers, custom DMOs and their categories, relationship cardinality and limits, and designing standard, streaming and real-time data graphs.
Model data in Data 360.
~8 min read · 25 practice questions ·
What the exam expects
- Map data lake objects (DLOs) to data model objects (DMOs) in Data 360 (formerly Data Cloud): planning steps, automapping, data type compatibility and the fields each category must map.
- Model the party subject area: Individual, contact points, Party Identification, Contact Point Digital Id, person accounts, and the right standard engagement DMOs.
- Prevent key collisions across sources with key qualifiers.
- Create, recategorize and delete custom DMOs, and explain what blocks removing a mapping.
- Design DMO relationships: cardinality, standard versus custom behaviour, status and limits.
- Design data graphs: primary DMO, calculated insights, child record limits, and scheduled, streaming or real-time refresh.
Key terms:
- Field mapping: the link from a DLO field to a DMO field on the mapping canvas.
- Party: the foreign key on contact point and Party Identification objects that references Individual Id.
- Fully qualified key: a source key plus a key qualifier field identifying its source.
- Cardinality: one-to-one or many-to-one structure of a DMO relationship.
- Data graph: a flattened, read-only JSON record combining fields from a primary DMO and its related objects.
Key facts
Sources per DMO field
- Detail
- One DLO field only
Engagement mapping save
- Detail
- Primary key and event date time
Party Identification match
- Detail
- Same type, name and number
Number DLO field
- Detail
- Maps to Number or Text
CSV column order
- Detail
- Field Label, Field API Name, Data Type, Primary Key
Category change
- Detail
- Profile ↔ Other only, if unused in segments or activations
Standard DMO deleted
- Detail
- Inactive; reactivates on remap
Relationship cardinality
- Detail
- One-to-one or many-to-one; fixed at creation
Child record limit
- Detail
- Default 100, maximum 1,000
Default graph refresh
- Detail
- Daily
Session length maximum
- Detail
- 48 hours
Sources for this section (10)
- Map Data Model Objectshelp.salesforce.com (opens in a new tab)
- Data Mapping Requirementshelp.salesforce.com (opens in a new tab)
- Data Types in Field Mappingshelp.salesforce.com (opens in a new tab)
- Create from CSVhelp.salesforce.com (opens in a new tab)
- Change the Categoryhelp.salesforce.com (opens in a new tab)
- Manage Objects and Field Mappingshelp.salesforce.com (opens in a new tab)
- DMO Relationshipshelp.salesforce.com (opens in a new tab)
- Manage Data Returnedhelp.salesforce.com (opens in a new tab)
- Create a Data Graphhelp.salesforce.com (opens in a new tab)
- Record Cachinghelp.salesforce.com (opens in a new tab)
- Why does a custom relationship vanish after you remap one of its fields?
- When can a calculated insight join a data graph?
- Why does a standard relationship not appear on the Relationships tab?
- Which object carries RampID values for a JSON-based activation-toolkit target?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Data 360 Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Data 360 Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (25 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams