Salesforce Decode
Salesforcedecode
Back to questions
Data CloudArchitect (Hardest)multi-orgenterprisearchitecturestrategy

Architect Data Cloud in a multi-org Salesforce estate

Real World Scenario

A conglomerate has 12 Salesforce orgs across regions. HQ mandates one enterprise customer view but regions resist centralizing operational CRM.

Expected Answer

• Position Data Cloud as analytical unification layer without forcing single CRM org • Ingest from all regional orgs via CRM Connector with org identifier dimension • Define global vs regional DMO extensions for market-specific attributes • Establish data residency partitions if EU/APAC data cannot co-mingle • Governance council with regional data stewards approving match rule changes • Activation back to regional orgs via Data Actions with scoped payloads • Avoid duplicating Data Cloud instances without clear legal/technical boundary

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Position Data Cloud as analytical unification layer without forcing single CRM org. Ingest from all regional orgs via CRM Connector with org identifier dimension. Pick based on your integration pattern and team capability. Data Cloud enables multi-org strategy that CRM consolidation failed to achieve—sell it as federation, not takeover. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Data Cloud enables multi-org strategy that CRM consolidation failed to achieve—sell it as federation, not takeover.