Study guide
Tento obsah zatím není dostupný ve vašem jazyce.
Study guide for chapter 4 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 4 is how data gets in: whether Data 360 pulls it or you push it, the connector that holds the credentials, the file door, the Ingestion API, and every other door by name.
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.
ING-2: Bringing data in from many sources
- I can tell a pull (Data 360 collects on a schedule) from a push (your systems send it), and name the doors on each side. (Pull or Push)
- I can ask the order of questions: where the data lives today, whether it can land in cloud storage, and only then whether it must be pushed. (The order of questions)
- I know File Upload is in every org: a CSV under 2 GB with at most 1,050 columns, and at most 100 file-upload streams and lake objects per org. (Start here: File Upload)
- I know an S3 stream ignores subfolders, and a wildcard file name brings in every matching file. (Which files)
- I can choose full refresh (wipe and rebuild: every file is complete) or upsert (update and add, never remove because a row is missing). (The refresh mode)
- I know that without “Log an error if no file is found,” a missing file is a success with 0 records. (When the file doesn’t come)
- I know the Ingestion API’s three steps: define a connector and a schema, create a stream, then push. (Define, stream, push)
- I know streaming takes small requests (under 200 KB) processed about every 3 minutes, and bulk takes files in a job (up to 150 MB each, 100 files a job), closed when the upload is done. (Streaming, Bulk)
- I know the streaming API has a test path that validates a payload without loading it. (Validate before you load)
- I can place each door: the CRM connector, Salesforce’s other clouds, cloud storage and SFTP, MuleSoft through the Ingestion API, the web and mobile SDKs, zero copy, and unstructured sources. (All the doors, in one table)
SA-3: The development lifecycle and its tooling
- I know a connector holds the address and the secret for one outside system, like a named credential in core, and that creating one needs the System Admin profile or the Data Cloud Architect permission set. (Like a named credential, Separate the concerns)
- I know a connector has to exist in each environment before anything that depends on it is deployed there. (One per environment)
- I know Installed Data Kits & Packages brings in streams that come already set up. (And hundreds more)
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.
- Pull when you can. With a pull, Data 360 owns the schedule and there’s no code of yours to keep running. (When Data 360 pulls)
- Every push has an owner after the project ends. Name who keeps the code, the token exchange and the retries. (When you push)
- Streaming needs a business reason. It’s billed by the row in both credit models, at more than batch costs (5,000 credits per million rows against 2,000 on the Data Services rate card), and it’s near real time, not real time. (Streaming)
- Separate the concerns: admins who hold secrets create connectors; data people only pick them. (Separate the concerns)
- Ask the business one question for the refresh mode: if a record is missing from the file, should it disappear? (The refresh mode)
- Use your own bucket, never a shared key. An IAM role that reads one bucket is the lesson itself. (The real door: your own bucket)
- Pick the slowest schedule the use case allows, and none at all in practice orgs. (How often: the schedule)
- Check the connector list before anyone builds, and its method column: many sources offer zero copy too. (And hundreds more)
- Trust, but verify what an AI assistant generates from your data. (Trust, but verify)
Words to Know
Section titled “Words to Know”| Term | In one line |
|---|---|
| Pull | Data 360 collects the data on a schedule, through a connector |
| Push | Your systems send the data in, through SFTP or the Ingestion API |
| Connector | A saved connection to one outside system: its address and its secret |
| File Upload | A CSV loaded by hand from your computer, in every org |
| Full refresh | Each load wipes and rebuilds: every file must be complete |
| Upsert | Each load updates existing rows and adds new ones; nothing is removed for being missing |
| Ingestion API | Data 360’s push door: streaming for small changes, bulk for large files |
| Zero copy | Data 360 reads data where it lives, without bringing it in |
| Private Connect | A private network path to a source, instead of the public internet |
Check Yourself
Section titled “Check Yourself”Short scenarios in the style of the course. Decide your answer before you open it.
1. A partner's system can only export a CSV every night. Which door?
Have it land in cloud storage (or an SFTP server), and let a stream pull it on a schedule. No push code to own. Reread The order of questions.
2. The nightly file didn't arrive, but the stream shows Success. What happened, and what would have caught it?
Without “Log an error if no file is found,” a missing file is a success with 0 records. Turn it on for every file stream. Reread When the file doesn’t come.
3. A file sometimes holds only the changed airports. Full refresh or upsert?
Upsert. With full refresh, every airport missing from a partial file would disappear. Reread The refresh mode.
4. A team wants to stream a year of flight history through the Ingestion API, 200 KB at a time. What do you suggest?
Bulk: open a job, upload files of up to 150 MB, close the job, and monitor it. Streaming is for small changes as they happen. Reread Bulk: the loading dock.
5. A deployment to production fails on a stream that reads from S3. What did the release plan miss?
The connector. It holds real credentials, so it has to exist in production before anything that depends on it is deployed. Reread One per environment.
6. The writer of the files moves to a new folder, with a subfolder per day. What breaks?
Subfolders are ignored, so the stream sees nothing; and files older than the last one ingested can be skipped. Keep the folder flat, and agree on names first. Reread Which files.
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.