Oracle Cloud Infrastructure Architect Professional Workshop — Lesson 1: OCI Organization, IAM, Compartments, Governance, and Multi-Region Strategy

Learning Objectives

• Explain the architecture, workflow, or business purpose behind regions, availability domains, fault domains, and location decisions.
• Apply tenancy design, compartments, identity domains, groups, policies, and federation and tagging, quotas, budgets, Cloud Guard, Security Zones, and governance in a controlled scenario.
• Validate outcomes and troubleshoot risks involving landing zones, account separation, deployment patterns, and design evidence.

Detailed Topics

• regions, availability domains, fault domains, and location decisions
• tenancy design, compartments, identity domains, groups, policies, and federation
• tagging, quotas, budgets, Cloud Guard, Security Zones, and governance
• landing zones, account separation, deployment patterns, and design evidence

Instructor Demonstration

Demonstrate regions, availability domains, fault domains, and location decisions within a multi-region customer platform migrating to OCI with strict isolation, recovery, performance, compliance, and cost requirements, then capture the exact configuration, command, transaction, report, model, query, code, or process evidence that proves the result for lesson 1.

Hands-On Exercise

Implement a controlled exercise covering tenancy design, compartments, identity domains, groups, policies, and federation and tagging, quotas, budgets, Cloud Guard, Security Zones, and governance, then introduce and resolve an exception involving landing zones, account separation, deployment patterns, and design evidence while preserving before-and-after evidence.

1. Confirm the environment, identities, inputs, dependencies, risks, and expected outcome.
2. Complete the course-specific configuration, development, analysis, or process workflow.
3. Capture settings, commands, data, outputs, logs, reports, screenshots, calculations, or test results.
4. Compare the observed result with acceptance criteria and document corrective action.

Scenario Analysis

• Identify the technical or business decision that must be made.
• Compare valid approaches and their security, performance, reliability, cost, compliance, and support trade-offs.
• Define rollback, recovery, ownership, communication, and evidence requirements.

Troubleshooting Guidance

Diagnose issues across regions, availability domains, fault domains, and location decisions, tenancy design, compartments, identity domains, groups, policies, and federation, tagging, quotas, budgets, Cloud Guard, Security Zones, and governance, landing zones, account separation, deployment patterns, and design evidence without making an unverified production change. Separate symptoms from causes, gather evidence, test the smallest reversible correction, rerun validation, and record preventive action.

Validation Checklist

• The requirement, scope, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by course-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply OCI Organization, IAM, Compartments, Governance, and Multi-Region Strategy in a realistic Oracle Cloud Infrastructure Architect Professional Workshop scenario and validate the result with documented evidence.