Study guide
תוכן זה אינו זמין עדיין בשפה שלך.
Study guide for chapter 8 of the Data 360 Architect course. Read the five modules first; this page helps you check what stuck.
About this study guide. It’s built only from this course’s own content and the published Salesforce exam guide’s list of objectives. It is never based on real exam questions, and it doesn’t claim to know what’s on the exam. If you’ve taken the exam, please don’t send me questions from it: the certification agreement forbids sharing them, and memorizing answers is the wrong way to become an architect.
This course covers the Data 360 Consultant exam, but the exam is just a step on the road. As architects, we go beyond it. Chapter 8 is the last step of Part 1: mapping the lake to the model, reference data one to one, people into the standard model, and the party that makes them ready for identity resolution.
For the Consultant Exam
Section titled “For the Consultant Exam”What this chapter covers of the Data 360 Consultant exam guide (opens in a new tab)’s objectives. Tick them off as you go. Each one links to where it’s taught.
HU-2: Modeling data
- I know data must be mapped to a data model object before segmentation, activation or analytics can use it, and only mapped fields can be used. (Nothing happens until it’s mapped)
- I know the Customer 360 Data Model is organized into subject areas, such as Party and Engagement, made of standard and custom data model objects. (The Customer 360 Data Model)
- I can map reference data one to one into a new custom data model object, from the lake object. (Airports and runways, all the way through)
- I know a field maps only to a compatible type: a date to a date, a number to a number or text, text to text, email, phone or URL. (Types)
- I know value suggestions are for Text fields only, up to 500 per org, and can take up to 24 hours to appear. (Value suggestions)
- I know a relationship’s cardinality can’t be changed after it’s created. (Relationships)
- I can map people data to the Individual and its contact points, and I know the primary key must be mapped before the mapping can be saved. (Step 1: the Individual)
- I know each contact point needs its own key and its Party, pointing to the Individual. (Step 2: the contact points)
- I know the mapping list is filtered by compatible categories. (The category still decides)
- I know Salesforce’s best practice for CRM contacts: map Contact to the Individual, with the contact ID as the Individual ID. (The same idea for the org)
- I know Party Identification matches people across sources by an ID’s type, name and number. (Party Identification)
- I know the phone is matched in E.164, Contact Point Phone’s Formatted E164 Phone Number. (The phone, formatted for matching)
As an Architect
Section titled “As an Architect”The consultant exam is the floor. This is what an architect takes from this chapter, beyond it.
- Two kinds of mapping: people into the standard model, so they can be unified and segmented; reference data one to one into custom objects. (Two kinds of mapping)
- Name a model object for what it is, not for its source, and do it when you create it. (Name it for what it is)
- Never put people in a custom object: identity resolution works on the standard Individual. (When a custom object is the right home)
- A line you didn’t draw is a line you haven’t checked. Automapping can draw every line, keys included; read the mapping before you trust it. (Step 1: the Individual)
- Read it right to left: from each object’s primary key back to the source, then the fields you need, then what’s unmapped. (Read it right to left)
- Don’t judge a mapping by the first page of Data Explorer: filter for the source you mapped. (Check it in Data Explorer)
- Agree on each ID’s type and name once, spelled the same in every source, or Party Identification won’t match. (The constants)
- Map only what a use needs: two custom fields on the Individual now, the rest left on the lake until a use needs them. (The pilots file)
Words to Know
Section titled “Words to Know”| Term | In one line |
|---|---|
| Customer 360 Data Model | Salesforce’s standard model, organized into subject areas |
| Data model object (DMO) | An object in the model: standard, or custom from your own data |
| Mapping | The lines from a lake object’s fields to a model object’s fields |
| Automapping | Data 360’s suggested mapping, from past pairs, matching names and synonyms |
| Individual | The standard object for a person |
| Contact point | A way to reach a person (email, phone, address), a child of the Individual |
| Party | The field on every person-related object that points to the Individual |
| Party Identification | An ID for matching across sources: its type, name and number |
| E.164 | The international phone format with the country code, used for matching |
| Cardinality | How many on each side of a relationship; can’t be changed once created |
Check Yourself
Section titled “Check Yourself”Short scenarios in the style of the course. Decide your answer before you open it.
1. A stream is running and its lake object is full, but a segment can't select anything from it. Why?
It isn’t mapped. Data must be mapped to a data model object before segments, insights or identity resolution can use it. Reread Nothing happens until it’s mapped.
2. A team puts pilots in a custom object, like the airports. What goes wrong later?
Identity resolution works on the standard Individual, so the pilots can’t be unified with the same people from other sources. People go into the standard model. Reread When a custom object is the right home.
3. A pilot has a work email and a personal email, and both contact point rows use the pilot ID as their key. What happens?
They collide: one email overwrites the other. Each contact point needs its own key; the pilot ID belongs in the Party. Reread Step 2: the contact points.
4. After mapping the pilots, the Individual's first page in Data Explorer shows only CRM contacts. Did the mapping fail?
Not necessarily. Filter for something only the pilots have, such as years flying greater than 1, before you decide. Reread Check it in Data Explorer.
5. One source writes "Pilot ID" and another "PilotID" as the identification name. Will Party Identification match them?
No. The type and the name have to be spelled exactly the same in every source. Agree on them once. Reread The constants.
6. You built a runway-to-airport relationship as one-to-one by mistake. Can you fix it?
Not by editing it: cardinality can’t be changed after the relationship is created. Decide it before you create it. Reread Relationships.
Explore
Section titled “Explore”- Salesforce Certified Data 360 Consultant Exam Guide (opens in a new tab), Salesforce Help: the official list of objectives and their weights. Always check the current version before you book the exam.