Study guide
Esta página aún no está disponible en tu idioma.
Study guide for chapter 5 of the Data 360 Architect course. Read the four 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 5 is your Salesforce orgs as sources: connecting them, the standard bundles, a custom object of your own, and how fresh the data is.
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.
SA-1: Permissions and org-wide settings
- I know the home org is connected automatically, with the alias Home, and its connection can’t be disconnected. (The home org connects itself)
- I know what an org needs before it connects: domain settings, API access, Salesforce’s IP ranges, and object and field permissions. (Before you connect)
- I know Data 360 reads the org through the Data Cloud Salesforce Connector permission set, used by a system user, and that what that user can’t see doesn’t come in. (Step 2: Give the connector access)
- I know Salesforce asks for View All Records and View All Fields on ingested objects, and access to related objects too, “even if you don’t ingest the related objects.” (Step 2: Give the connector access)
ING-2: Bringing data in from many sources
- I know another org’s alias is up to 15 characters, can’t be changed, names its streams and lake objects, and must match across orgs if you use data kits. (The alias: one chance to name it)
- I know deleting a CRM connection deletes all the data it brought in, and a sandbox refresh means reauthenticating. (Two things that can surprise you)
- I know a standard data bundle is used in two steps: install it, then create its streams. (Two steps: install, then stream)
- I know a custom object should be Deployed: one still In Development keeps its CRM stream out of streaming mode. (Step 1: Finish it in core)
- I can create a CRM stream for a custom object: the org and objects (up to 30), the category, the lake object’s name, the fields, the data space. (Step 3: Create the CRM data stream)
- I know a new field joins a running stream as a source field, after the connector can read it; and disabling a field clears its data. (When the object changes)
- I know CRM streams refresh incrementally about every 10 minutes, and that a stream runs in batch or, if eligible, streaming mode. (What changed, Batch or streaming)
- I can name what keeps a stream in batch: batch-ingested formula fields, an object still In Development, a Deleted Record lake object, other users in the connector’s permission set. (Batch or streaming)
- I know what Accelerated Data Ingest does: CRM data into the real-time layer, in about a minute, expected rather than guaranteed. (Accelerated Data Ingest)
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.
- Decide each source org’s alias once, the same in every environment. Built by hand with different aliases in dev and production, the names collide when you move to data kits, and the fix is a rebuild. (The alias)
- Preparing an org is core work, often another team’s. Plan who does it, where, and by when. (Before you connect)
- Read a bundle’s mappings right to left, from each model object’s key back to the source. (Read it right to left)
- A bundle doesn’t know your business. Keep only the fields you need, and decide before you deploy: removing it later is hard. (Decide before you deploy)
- Check the connector’s access, don’t assume it. In my org the new object was readable without View All Fields; that covers today’s fields, not tomorrow’s. (Step 2)
- Renaming a lake object is a trade-off: cleaner in one org, but the custom name isn’t kept when you deploy to another. (Step 3)
- Add fields, don’t rebuild. Deleting a stream can unravel the lake object, transforms and model behind it. (When the object changes)
- Ask how soon Data 360 must know, for each object: within the hour, within minutes, or within about a minute. Every step costs more. (Freshness still costs credits)
Words to Know
Section titled “Words to Know”| Term | In one line |
|---|---|
| Home org | The org Data 360 is provisioned on; its connection is created for you, with the alias Home |
| Alias | The name given to a connected org, used in its streams’ and lake objects’ names; can’t be changed |
| Standard data bundle | A ready set of CRM streams, lake objects and mappings for standard objects |
| Data Cloud Salesforce Connector | The permission set that says what Data 360 can read in the org |
| Batch mode | A CRM stream that checks for changes every 10 to 15 minutes |
| Streaming mode | A CRM stream that reflects changes as they’re made, for eligible objects |
| Accelerated Data Ingest | CRM data into the real-time layer in about a minute |
| External ID | A core field that marks a key from another system; Unique is a separate box |
Check Yourself
Section titled “Check Yourself”Short scenarios in the style of the course. Decide your answer before you open it.
1. A team connected the same org by hand in development as "SalesDev" and in production as "Sales". Now they want to deploy with data kits. What happens?
The names don’t match, so nothing lines up from one environment to the next, and the alias can’t be changed. Decide each org’s alias once and use it everywhere. Reread The alias: one chance to name it.
2. Someone deletes a CRM connection to tidy up. What else goes?
All the data Data 360 ingested from that org, and those records leave the unified profiles at the next identity resolution run. Reread Two things that can surprise you.
3. A new field was added to a custom object, but it never shows up in Data 360. What's missing?
Two steps: the connector needs to be able to read the field, then the field is added to the existing stream as a source field. Reread When the object changes.
4. A stream for a custom object stays in batch mode. Name two things to check.
Whether the object is still In Development, and whether the stream has batch-ingested formula fields (also: a Deleted Record lake object, or other users added to the connector’s permission set). Reread Batch or streaming.
5. The business wants every CRM change in Data 360 within seconds, for every object. What do you ask?
How soon each object really needs to be known. Batch is within the hour, streaming within minutes, and Accelerated Data Ingest about a minute; each step costs more downstream. Reread Freshness still costs credits.
6. After a sandbox refresh, the sandbox's streams start failing. Why?
The refresh gave the sandbox a new org ID, which no longer matches the connection. Reauthenticate it, and put that step in the refresh checklist. Reread Two things that can surprise you.
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.