Single-org versus multi-org strategy trade-offs
How to decide between one org and several: the operating-model test, the isolation, regulatory and redundancy triggers that justify multi-org, the cost and security multipliers it brings, and how to govern either choice with a CoE, packages and hub-and-spoke integration.
Given a customer landscape and their requirements, evaluate business, technical, and architectural considerations which support the defined org strategy.
~7 min read · 13 practice questions ·
What the exam expects
- Recommend one org or several from how standardized and integrated the business processes are.
- Separate valid multi-org triggers (regulatory or contractual isolation, data residency, recovery beyond the platform) from weak ones (backlog, independence, limits that could be raised).
- Build a multi-org total cost of ownership model and explain the security governance it multiplies.
- Choose between platform-managed redundancy, active-passive and active-active, and between point-to-point and hub-and-spoke integration.
- Describe what a single org with several lines of business needs, and how a CoE and reference architecture stop org sprawl.
Key terms: operating model (the business's mix of process standardization and process integration); hub-and-spoke (one org holds shared master data for the others, integrated through middleware); active-passive (a synchronized but idle secondary org takes over in an outage); TCO multiplier (costs that repeat per org); trust boundary (a crossing where data must be authenticated, authorized and monitored).
Key facts
- Detail
- As few orgs as possible
- Detail
- Not a reason to split; fix with CoE roadmap and tiered admin
- Detail
- Talk to the Salesforce account team; some limits can be raised
- Detail
- Five queued or active per org; flex queue holds up to 100 in Holding
- Detail
- 2-3x for admin, release management, monitoring, compliance
- Detail
- Single region with platform-managed redundancy suffices for most
- Detail
- Separate paid offering, not in any standard edition
- Detail
- A trust boundary needing explicit authentication and authorization
- Detail
- Unlocked package with version control as source of truth
Sources for this section (6)
- Single-org versus Multi-org Strategydeveloper.salesforce.com (opens in a new tab)
- Execution Governors and Limitsdeveloper.salesforce.com (opens in a new tab)
- License Optimization - Patternsarchitect.salesforce.com (opens in a new tab)
- Reliabilityarchitect.salesforce.com (opens in a new tab)
- Trustarchitect.salesforce.com (opens in a new tab)
- Unlocked Packagesdeveloper.salesforce.com (opens in a new tab)
- Why is a growing backlog across lines of business not a reason for a second org?
- When does Well-Architected consider a multi-org pattern justified for reliability?
- Which costs must the multi-org side of a TCO model include?
- Why do two orgs make security governance harder than one?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Development Lifecycle and Deployment Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform Development Lifecycle and Deployment Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (13 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams