Oracle Cloud Infrastructure Architect Associate — Lesson 1: OCI Regions, Compartments, IAM, and Governance Foundations

Technical Scope

• regions, availability domains, fault domains, and scope
• tenancy, compartments, tags, quotas, and budgets
• users, groups, policies, dynamic groups, and federation
• security zones, Cloud Guard awareness, and governance

Instructor Demonstration

Demonstrate regions, availability domains, fault domains, and scope inside a customer-facing service revised for private connectivity, regulation, growth, regional failure, and budget limits, then capture the exact configuration, command, transaction, report, or code evidence that proves the result.

Applied Workshop

Implement a controlled workshop covering tenancy, compartments, tags, quotas, and budgets and users, groups, policies, dynamic groups, and federation, then test a failure or exception involving security zones, Cloud Guard awareness, and governance.

1. Confirm environment, identity, data, dependencies, and expected result.
2. Complete the product-specific implementation or analysis.
3. Capture commands, configuration, output, logs, transactions, or reports.
4. Explain the operational, security, performance, or business trade-off.

Validation Standard

The OCI Regions, Compartments, IAM, and Governance Foundations result must be reproducible, traceable to approved inputs, and consistent with the expected Oracle product behavior.

• The intended target and ownership are verified.
• The result is supported by reproducible evidence.
• Security, performance, reliability, and support impact are reviewed.
• Unexpected behavior is investigated before acceptance.

Failure Analysis

Diagnose issues in regions, availability domains, fault domains, and scope, tenancy, compartments, tags, quotas, and budgets, users, groups, policies, dynamic groups, and federation, or security zones, Cloud Guard awareness, and governance without making an unverified production change.

Learners isolate the smallest proven cause, apply a reversible correction, rerun validation, and record the preventive action.