Study guide

8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

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

8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints

Key Takeaways Explain This Topic AI

A Resource Manager stack is the set of OCI resources that corresponds to one Terraform configuration, and it lives in one compartment in one region.

Only one job at a time can run on a stack, because Resource Manager locks the stack's state while a job runs.

Drift detection reports resources whose real configuration differs from the stack's last executed configuration, and it can be limited to specific resource addresses.

Resource discovery captures existing resources in a compartment as Terraform configuration and state files.

Resource Manager private endpoints let Terraform reach non-public resources, such as private instances for remote-exec or a private Git server.

Last updated: October 2026

What Resource Manager Adds to Terraform

Running Terraform on laptops creates problems at enterprise scale: state files get lost or copied, two people run apply at once, and credentials sit on personal machines. OCI Resource Manager solves these by running Terraform jobs inside OCI, storing the state, and controlling access with IAM.

Core Concepts

Concept Meaning

Stack The collection of OCI resources for a Terraform configuration. A stack resides in one compartment and one region, although the configuration can create resources in other regions.

Configuration Terraform files (HCL or JSON) that define the resources, data sources, and variables.

Job An instruction to run a Terraform action on a stack. Jobs keep history: plan jobs store execution plans, and apply jobs store configuration snapshots and state.

State The JSON state file that Resource Manager generates and stores for each stack.

Configuration source provider Connection details for a source control system that holds the configuration.

Template A prebuilt configuration, provided by Oracle or shared privately within your tenancy.

Private endpoint Network information that lets Resource Manager reach non-public resources.

Creating a Stack: Where the Configuration Comes From

  • Source Typical use
  • Local .zip file Quick uploads of a configuration bundle
  • Object Storage bucket Configurations produced by a build pipeline

Source code control (GitHub, GitLab, Bitbucket Cloud, Bitbucket Server, OCI DevOps code repositories) CI/CD: the stack always uses a versioned branch

  • Oracle-provided or private templates Standard architectures shared across teams
  • Existing compartment Resource discovery turns deployed resources into a new stack
  • Resource creation page Saving a Console form as a stack instead of creating the resource directly

You can also add a Deploy to Oracle Cloud button to a Git repository's README so users launch the configuration as a stack with one click.

Variables and the Schema Document

Stack variables are passed to the Terraform job as environment variables. A schema document ( schema.yaml ) in the configuration describes the variables for the Console, so users see friendly fields, drop-down lists of compartments or VCNs, validation, and grouping instead of raw text boxes. Inside Resource Manager, the provider "oci" block only needs the region , because the service supplies authentication.

Jobs

Resource Manager supports these job types:

  • Job What it does
  • Plan Generates and stores an execution plan
  • Apply Creates or updates resources, optionally using an approved plan job
  • Destroy Deletes the stack's resources
  • Import state Imports an existing Terraform state file into the stack

Job lifecycle states are Accepted, In Progress, Succeeded, Failed, Canceling, and Canceled. Only one job at a time can run on a stack , because Resource Manager locks the stack's state during a job. This replaces the manual locking discipline that local Terraform requires. If a job fails because of a temporary problem in a downstream service, it retries according to the Go SDK's default retry policy.

Drift Detection

Drift is the difference between the real state of the infrastructure and the stack's last executed configuration, for example when someone adds a tag or changes a security rule in the Console. A drift detection run reports the drift status of each resource. You can limit the run to specific resource addresses , such as oci_core_instance.test_instance[3] , which combines the resource type, the resource name from the configuration, and an index.

Drift detection only reports. To fix drift, you either update the configuration to match the change or run an apply job to restore the configured values.

Resource Discovery: Importing Existing Infrastructure

Many organizations start with resources built by hand. Resource discovery captures deployed OCI resources as Terraform configuration and state files. With it you can:

Move manually managed infrastructure under Resource Manager control.

Learn how Terraform represents OCI resources in HCL.

Duplicate or rebuild existing infrastructure in another compartment.

Private Endpoints and Remote-Exec

Terraform's remote-exec provisioner runs commands on an instance after it is created, for example to install software. If the instance has only a private IP, Resource Manager cannot reach it over the internet. A Resource Manager private endpoint gives jobs a network path into a VCN subnet so they can:

Run remote-exec against private compute instances.

Pull configurations from a private Git server in OCI or on-premises (over VPN or FastConnect); you import the server's SSL certificate into the Certificates service.

Reach other private endpoints, such as a private OKE API endpoint.

Managing private endpoints requires permission to manage Resource Manager private endpoints and to use the related network resources.

Templates and Governance

Private templates let a platform team publish approved configurations, such as a hardened three-tier application or a standard network, to everyone in the tenancy. Combined with IAM ( manage orm-stacks and manage orm-jobs for operators, read-only access for auditors), templates make the approved architecture the easiest one to deploy.

Loading diagram... Resource Manager Stack Lifecycle