Study guide

9.2 Organizations Management, Governance Rules & Compartment Quotas

OCI 2026 Architect Professional 1Z0-997-26

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview & Architecture Foundations

1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs

2 Chapter 2: High Availability & Resilient Design

2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)

3 Chapter 3: Full Stack Disaster Recovery

3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness

4 Chapter 4: Container Instances, OCIR & OCI DevOps

4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies

5 Chapter 5: OCI Kubernetes Engine (OKE)

5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage

6 Chapter 6: Serverless Functions & API Gateway

6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans

7 Chapter 7: Messaging & Event-Driven Design

7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out

8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager

8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

9 Chapter 9: Identity & Multi-Tenancy Governance

9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas

10 Chapter 10: Security Posture with Cloud Guard & Security Zones

10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning

11 Chapter 11: Secure Access & Network Protection

11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT

12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault

12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation

13 Chapter 13: Base Database Service & Autonomous AI Database

13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database

14 Chapter 14: Recovery Service, Global Distribution & OCI Cache

14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication

15 Chapter 15: Monitoring, Alarms & Notifications

15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery

16 Chapter 16: Logging, Audit, Connector Hub & Search

16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability

9.2 Organizations Management, Governance Rules & Compartment Quotas

Key Takeaways Explain This Topic AI

Organizations Management lets a parent tenancy create or invite child tenancies, map subscriptions to them, and report costs across all tenancies in the organization.

The parent tenancy must be associated with a paid Oracle Universal Credits subscription.

Governance rules can enforce allowed regions, quota policies, and tag namespaces or tag defaults in child tenancies.

Resources created by a governance rule are locked in the child tenancy, so child administrators cannot modify them.

An allowed-regions rule stops new region subscriptions but does not remove regions a child tenancy already subscribes to.

Last updated: October 2026

Why Multiple Tenancies

Compartments isolate resources inside one tenancy, and for many organizations that is enough. Some situations call for separate tenancies :

Strict data isolation between business units, subsidiaries, or customers.

Separate identity domains and administrators for an acquired company.

Isolated sandboxes where experiments cannot affect production identity or policies.

Regulatory requirements that demand a hard administrative boundary.

The challenge is that separate tenancies normally mean separate contracts, separate bills, and separate, inconsistent guardrails. Organizations Management solves this by linking tenancies into one organization.

Parent and Child Tenancies

Role Description

Parent tenancy The tenancy associated with the primary funded subscription, which must be a paid Oracle PaaS and IaaS Universal Credits subscription. It manages cost and governance for the organization.

Child tenancy A tenancy that joins the organization. The parent manages its cost and governance.

A child tenancy joins in one of two ways:

Created by the parent. The parent creates a brand-new tenancy. It consumes from the organization's default subscription unless another subscription is selected. Its home region must be one of the parent's subscribed regions, and it inherits the parent's current default service limits , although each child then has its own limits that are not shared with other tenancies.

Invited. An existing standalone tenancy is invited to join the organization and change its default subscription.

The parent uses subscription mapping to assign subscriptions to any child tenancy.

Central Cost Management

Because the tenancies share a commitment, the parent can analyze and report spending across every linked tenancy using Cost Analysis , cost and usage reports , and Budgets alerts. This avoids the overages that happen when each tenancy has its own small commitment.

Governance Rules

A governance rule is an enforcement that the parent tenancy creates to govern a resource in child tenancies. When a rule is attached, a corresponding resource is created in the target tenancy and locked . Users in the child tenancy see a lock icon and cannot modify it. To change it, the parent must update the rule.

Oracle supports three types of governance rules:

Rule type What it enforces Example

Allowed regions The regions a child tenancy may subscribe to Only EU regions for a subsidiary that must keep data in the EU

Quota policy Tenancy-level quotas that limit or disable services zero compute-core quotas in tenancy ; set compute-core quota to 20 in tenancy

Tags A shared tag namespace or a tag default A mandatory CostCenter tag on every resource

Points that exam questions test:

An allowed-regions rule prevents subscribing to other regions, but if the child already subscribes to a region not on the list, that subscription remains and resources can still be deployed there.

If you change a resource in the parent that a rule was built from, such as a tag namespace, you must update the governance rule for the change to reach child tenancies.

Rules can be attached to specific tenancies or to all current and future tenancies that have joined organization governance. Tenancies can be opted in to or out of organization governance.

Rules can be attached while creating a child tenancy, so new tenancies start with guardrails already in place.

Compartment Quotas Inside a Tenancy

Governance rules work at the tenancy level. Inside each tenancy, administrators use compartment quotas to divide capacity between teams. Quotas are written as policy-like statements: zero compute-core quotas in tenancy

  • set compute-core quota standard-e4-core-count to 40 in compartment Production
  • unset compute-core quota standard-e4-core-count in compartment Sandbox

set defines a maximum.

zero blocks the resource entirely.

unset removes a quota inherited from a parent compartment's statement.

Quotas differ from service limits . Service limits are set by Oracle for the tenancy and can be raised with a limit increase request. Quotas are set by your administrators to stay below those limits and to stop one team from consuming everything.

Designing a Multitenancy Organization

A common enterprise pattern combines both layers:

A parent tenancy holds the subscription, billing, and governance rules.

Child tenancies isolate business units or regulated workloads.

Governance rules set allowed regions , tag defaults , and baseline quotas for every child.

Inside each child, compartments , IAM policies , Security Zones , and Cloud Guard provide the finer-grained controls covered in the rest of this chapter.

This design keeps the strong isolation of separate tenancies while preserving central visibility and control.

Two planning details are worth remembering. SaaS or multicloud subscription services can be activated in the parent or in a child tenancy, but resources against those subscriptions can only be provisioned in the tenancy where they were activated. And an invited child tenancy must be removed from the organization with its original subscription before it can be deleted, so plan tenancy lifecycles before inviting them.

Loading diagram... Organization with Governance Rules