Administering Cloud EPM: The Platform Beneath the Business Processes · Module 3 · Cloud Account, Identity Domains and Regions
Lab solution walkthrough
Lesson 40 of 201 · 20 min
The worked design, reasoned rather than announced. Cloud account structure, and why. Regions, driven by the written residency constraint — not by latency, and not by where the head office is. Identity domains, with a stated reason for each. The non-production question, resolved — and the resolution names whose decision it was, because that is what the disagreement in the brief was testing. The identity team's "one or two" is a real constraint on the answer, not colour. Then compartments, environments mapped to domains and regions, and the decision log written out. The CFO's "next day" remark: recorded as an expectation to be tested against the continuity design in Module 12, not adopted as a requirement here. Writing it down without acting on it is the correct move, and it is the one most people miss. Common wrong answers. A domain per business process — the commonest, and it fails…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 3 · Cloud Account, Identity Domains and Regions
- 1What we are building
- 2The decisions you cannot undo
- 3The identity object model
- 4Identity domains — the central decision
- 5Regions and data residency
- 6Compartments
- 7Running the estate design workshop
- 8Four worked estate structures
- 9Activating: creating a new cloud account
- 10Activating: adding to an existing account
- 11Touring the Oracle Cloud Console
- 12Enabling multifactor authentication
- 13Subscribing to and replicating regions
- 14Creating a compartment
- 15Creating an identity domain
- 16Identity domain administrators
- 17What breaks
- 18Lab briefing: Northwind Group
- 19Lab solution walkthrough