Choosing initial Data 360 use cases
How to pick a first Data 360 use case: start small instead of a big-bang launch, answer the requirement and data questions first, anchor on unifying customers, reserve real-time for problems that need it (and build its prerequisites), and choose ingestion or Zero Copy federation.
Identify initial use cases for Data 360.
~8 min read · 9 practice questions ·
What the exam expects
- Recommend a phased start (one small, actionable use case) over a big-bang launch, and explain why it makes ROI visible.
- List the questions to answer before committing to a first use case: outcomes, data needed and its accessibility, residency and compliance, owners, timeframe and credit-heavy features.
- Recognize unifying customers across systems as the anchor use case that most others depend on.
- Judge whether a problem needs real-time Data 360, and name the prerequisite (a real-time data graph) for real-time insights and segments.
- Choose between ingesting data and Zero Copy federation for a first use case, including when to turn on caching.
Key terms: use case is a business scenario with a data-driven action and measurable outcome; real time (end-to-end sub-second) means data is processed and delivered in under one second; real-time data graph is a precalculated, continuously refreshed view of DMO data that real-time features require; data federation queries external data where it lives without copying it; caching (acceleration) temporarily stores federated data in a DLO to lower latency.
Key facts
- Detail
- Small, actionable, shows value quickly; larger use cases follow
- Detail
- Include data residency or compliance concerns, such as HIPAA
- Detail
- Identify credit-heavy features, such as real-time ingestion, before implementation
- Detail
- End-to-end sub-second: processed and delivered in under one second
- Detail
- Real time can be costly; plan credit consumption first
- Detail
- A real-time data graph on a Profile DMO, such as unified individual
- Detail
- Standard refreshes on a schedule; real-time refreshes continuously
- Detail
- Live query; zero data persisted
- Detail
- Query federation only; lowers latency, impacts cost; file federation always live
Sources for this section (5)
- Measure the Value of Data 360trailhead.salesforce.com (opens in a new tab)
- Justify Your Investment in Data 360trailhead.salesforce.com (opens in a new tab)
- Identify Real-Time Use Cases for Data 360trailhead.salesforce.com (opens in a new tab)
- Explore Real-Time Features in Data 360trailhead.salesforce.com (opens in a new tab)
- Explore Use Cases for Zero Copy Data Federationtrailhead.salesforce.com (opens in a new tab)
- Why does Salesforce recommend a small first use case?
- When is a problem a good fit for real-time Data 360?
- What must exist before real-time insights and segments can be used?
- When should caching be turned on for federated data?
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 (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams