Regions and data residency

What region selection determines: where the data physically resides. That is the whole thing. It is not a latency question. EPM is not latency-sensitive the way a transactional system is. Choosing a region for proximity when residency requires otherwise is the wrong trade — and it is the commonest way this decision goes wrong, because latency is the consideration a technical person reaches for first. So the question is: does this organization have a legal, regulatory or contractual obligation about where its data sits? Finance, HR-adjacent and public sector organizations frequently do. And the person who knows is not in your workshop by default. Get them in. Subscribing to and replicating regions — and what replication is for: availability and disaster recovery posture, covered properly in the continuity module. Where your secondary copy sits is a residency question too. And the permanence: moving an environment between regions means creating a…

In this module: Module 3 · Cloud Account, Identity Domains and Regions

1. 1What we are building
2. 2The decisions you cannot undo
3. 3The identity object model
4. 4Identity domains — the central decision
5. 5Regions and data residency
6. 6Compartments
7. 7Running the estate design workshop
8. 8Four worked estate structures
9. 9Activating: creating a new cloud account
10. 10Activating: adding to an existing account
11. 11Touring the Oracle Cloud Console
12. 12Enabling multifactor authentication
13. 13Subscribing to and replicating regions
14. 14Creating a compartment
15. 15Creating an identity domain
16. 16Identity domain administrators
17. 17What breaks
18. 18Lab briefing: Northwind Group
19. 19Lab solution walkthrough