Salesforce Data Management25% of the exam

Multi-org designs: cross-org adapter, consolidation, Data Cloud One

How to use data across several Salesforce orgs: the cross-org adapter for in-place access, Bulk API 2.0 extraction or middleware for aggregation and sync, External ID cross-references for org consolidation, and Data 360 provisioning with a Data Cloud One home org, companion orgs or data sharing between instances.

Official exam objective
Given a customer scenario, recommend a design to effectively consolidate and/or leverage data from multiple Salesforce instances.

~8 min read · 18 practice questions ·

What the exam expects

  • Decide whether one org or several fits, then pick the org-to-org pattern from the requirement: view or edit in place, aggregate for reporting, or keep records in sync.
  • Know what the cross-org adapter can't carry over and what still runs in the target org.
  • Plan an org consolidation load with source-Id External IDs, parent-before-child order and an Id cross-reference for polymorphic fields.
  • Choose the Data 360 home org, Data Cloud One or multiple instances with data sharing, and explain companion org limits, credits, region and latency.

Key terms: cross-org adapter (Salesforce Connect adapter that reads another org through the REST API); home org (the org that holds the Data 360 license and instance); companion org (an org connected to the home org through Data Cloud One); data space (a logical container of data and metadata); data share (zero-copy sharing of chosen objects between Data 360 instances).

Key facts

Salesforce to Salesforce
Detail
Reached end of life
Platform events between orgs
Detail
Not optimal; can't listen between orgs for the same event
External object limits
Detail
No formula or roll-up references; no Activities, Events or Tasks
Polymorphic fields on upsert
Detail
WhoId, WhatId and custom object Owner can't map to External IDs
Data 360 region
Detail
Set by the location of the org that receives the license
Companion org ingestion
Detail
Not allowed; home org only
Companion org credits
Detail
Consumed from the home org; per-org view in Digital Wallet
Data shares
Detail
Zero copy; tags not shared
Sources for this section (4)
  • Why isn't a platform event pair a good org-to-org sync design?
  • When is a new, dedicated Data 360 home org justified?
  • Why might European companion org users see slower unified profile queries?

The questions are free to read. Answers with their sources and self-grading are included with the pack.

Keep reading with the Platform Data Architect pack

  • Core concepts
  • Exam traps
  • Worked scenario

The pack includes:

  • All 21 lessons of the Platform Data Architect 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

Practice for the Platform Data Architect exam