Data Source Connection and Ingestion18% of the exam
Data streams, connectors and ingestion settings
Which connector fits each source, the one-time choices on a data stream (category, primary key, event time), refresh modes and schedules per connector, Ingestion API schema and delete rules, and the settings that cut ingestion credits.
Describe processes and considerations for data ingestion from varied sources into Data 360.
~7 min read · 20 practice questions ·
What the exam expects
- Pick the connector for a source: Salesforce CRM, Marketing Cloud Engagement, cloud storage, local file upload, Ingestion API, Web and Mobile App, or an unstructured connector.
- Set a data stream's one-time choices correctly: category, primary key (including composite keys), event time field and record modified field.
- Choose refresh modes and explain each connector's schedule, including CRM batch versus streaming and Marketing Cloud Engagement extract modes.
- Plan Ingestion API schema changes, record deletes and credit-saving settings.
Key terms:
- Data stream: a connection plus the data it ingests into a DLO.
- Category: Profile, Engagement or Other; fixed once the stream is saved.
- Event time field: the immutable date that orders Engagement records.
- Record modified field: the timestamp that stops older records overwriting newer ones.
- Starter data bundle: a Salesforce-defined stream definition already mapped to the data model.
Key facts
Category
- Detail
- Can't change after the stream is saved
CRM incremental refresh
- Detail
- Every 10 minutes; periodic full refresh off by default
CRM full refresh interval
- Detail
- None, 10, 25 or 50 days
Engagement history
- Detail
- 90 days when MCE streams are created
MCE full extract
- Detail
- Up to 100 million rows
Local file upload
- Detail
- Under 2 GB; up to 100 upload streams; primary key uniqueness not enforced
Cloud storage schedule
- Detail
- 5-, 15- or 30-minute intervals available
Ingestion API streaming
- Detail
- 200 KB per request; 200 records per delete request
Deletes
- Detail
- Require Upsert; no cascading
Schema update
- Detail
- No type changes; all existing fields present
Sources for this section (9)
- Categoryhelp.salesforce.com (opens in a new tab)
- Data Stream Schedulehelp.salesforce.com (opens in a new tab)
- Full refresh intervalhelp.salesforce.com (opens in a new tab)
- MCE connectorhelp.salesforce.com (opens in a new tab)
- Limitshelp.salesforce.com (opens in a new tab)
- Upload a filehelp.salesforce.com (opens in a new tab)
- Refresh modeshelp.salesforce.com (opens in a new tab)
- Delete Ingested Recordshelp.salesforce.com (opens in a new tab)
- Schema requirementsdeveloper.salesforce.com (opens in a new tab)
- Why must the event time field be immutable?
- When does a Salesforce CRM data stream stay in batch mode?
- Why does deleting a profile record leave its engagement records behind?
- How do you carry a text field as a number in an Ingestion API schema?
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 (20 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams