Data Source Connection and Ingestion18% of the exam
Zero Copy, data shares and clean rooms
Zero Copy in both directions: query and file federation bring external data in (live or accelerated), data shares send Data 360 objects out to Snowflake, Databricks, BigQuery, Redshift or another Data 360 org, and clean rooms let two parties query each other's data without exposing raw records.
Describe Data 360's data collaboration capabilities, including Zero-Copy.
~7 min read · 18 practice questions ·
What the exam expects
- Name the Zero Copy direction a scenario needs: federation to bring external data in, a data share to expose Data 360 data to an external lake or warehouse.
- Choose live query federation, accelerated query federation or file federation from query frequency, change rate, volume and credit cost.
- Predict which Data 360 features work on federated objects, including when caching is required.
- Configure data shares and targets, including governance, consent, cross-region credits and sharing between Data 360 orgs.
- Recommend a clean room and explain what each party contributes and receives.
Key terms:
- Query federation: Data 360 queries an external system through its compute layer, live or from a cache.
- Acceleration: caching federated data in a Data 360 DLO on a refresh schedule.
- File federation: Data 360 reads files in the external storage layer with its own compute.
- Data share / data share target: a set of Data 360 objects, and the connection to the external system that receives it.
- Clean room: a collaboration where two parties run permitted queries on each other's data while raw records stay private.
Key facts
Cache interval
- Detail
- 15 minutes to 7 days
Caching default
- Detail
- Off; edit the data stream to enable
Incremental cache refresh
- Detail
- Upserts only, no deletes
Cache credits
- Detail
- Batch Data Pipeline usage type, plus storage
Same-region AWS file federation
- Detail
- No credits for rows accessed
Shareable objects
- Detail
- DLOs, DMOs, calculated insight objects
Governance on shares
- Detail
- Not honored; apply at the target
Org-to-org shared objects
- Detail
- Arrive as DLOs in the receiving org
Segment overlap threshold
- Detail
- Minimum 100 matched individuals
Sources for this section (6)
- Compare Data Federation Methodshelp.salesforce.com (opens in a new tab)
- Caching or Accelerationhelp.salesforce.com (opens in a new tab)
- Federation billinghelp.salesforce.com (opens in a new tab)
- Data Shareshelp.salesforce.com (opens in a new tab)
- Share Data Between Data 360 Orgshelp.salesforce.com (opens in a new tab)
- Segment Overlap Templatehelp.salesforce.com (opens in a new tab)
- Why must a query-federated object be accelerated before a data action can fire on it?
- When does a query from an external data share consume Data 360 credits?
- What must the receiving org do to get objects shared by another Data 360 org?
- Why can't a DMO mapped to an external DLO join a Databricks data share?
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 (18 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams