Study guide

4.1 Containerization, Microservices & OCI Container Instances

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

4.1 Containerization, Microservices & OCI Container Instances

Key Takeaways Explain This Topic AI

OCI Container Instances is a serverless compute service that runs containers without managing servers, with the same isolation as virtual machines.

A single container instance can run up to 60 containers, which share the instance's flexible-shape OCPUs and memory.

The container restart policy can be Always (the default), Never, or On failure; if all containers exit and none restart, the container instance shuts down.

Container Instances supports File Storage volumes, empty-directory volumes backed by memory or ephemeral storage, and configuration-file volumes.

Stopping a container instance pauses billing; Creating, Failed, and Inactive states are not billed, while Active and Updating are billed.

Last updated: October 2026

From Monoliths to Microservices

A microservice architecture splits an application into small, independently deployable services, each owning its own data and exposing a well-defined API. Containers are the natural packaging unit: an image bundles the code, runtime, and libraries so the same artifact runs in development, test, and production. On OCI, a typical cloud-native flow looks like this:

Developers commit code to a repository.

An OCI DevOps build pipeline builds a container image and pushes it to OCI Container Registry (OCIR) .

A deployment pipeline releases the image to a runtime: Container Instances , OKE , or OCI Functions .

API Gateway , Streaming , Queue , and Events connect the services, and Monitoring and Logging observe them.

Key design principles that exam scenarios test:

Statelessness : keep session state out of the container (in a database, OCI Cache, or Object Storage) so instances can be replaced or scaled freely.

Loose coupling : communicate through APIs, queues, or event streams rather than shared databases.

Independent deployment : each service has its own pipeline and versioned image.

Observability by design : every service writes logs and metrics in a consistent format.

Choosing a Container Runtime

Requirement Best fit Why

Run one or a few containers with no orchestration Container Instances Serverless; specify images, shape, and networking only

Many services, service discovery, rolling updates, autoscaling of pods OKE Full Kubernetes control plane managed by Oracle

Short, event-driven code with automatic scale-to-zero OCI Functions Pay per invocation; synchronous calls up to 300 seconds

Batch job that runs for hours Container Instances or OKE jobs No function time limit; billed only while running

OCI Container Instances

Oracle describes Container Instances as a serverless compute service that runs containers without managing any servers , on compute optimized for containers, with the same isolation as virtual machines . It suits APIs, web applications, CI/CD build and deployment jobs, automation tasks, data and media processing jobs, and development or test environments that do not need Kubernetes.

Shapes and Resource Allocation

A container instance uses a flexible shape , such as CI.Standard.E4.Flex , where you choose the number of OCPUs and the amount of memory. Network bandwidth and the number of VNICs scale with the OCPU count. You can give the containers all of the CPU and memory of the shape, or set per-container limits so one container cannot starve another. For example, a WordPress container and a MySQL container can each be limited to half of the instance's resources.

Multiple Containers per Instance

One container instance can run up to 60 containers . Containers in the same instance share its CPU, memory, and network namespace , so one container can reach another over localhost (Oracle's tutorial connects a WordPress container to a MySQL container at 127.0.0.1 ). They can also share volumes, which makes it easy to run an application with a sidecar, such as a log forwarder. Oracle recommends a managed database service rather than a database container for production.

Restart Policy and Graceful Shutdown

The container restart policy applies when a container exits:

  • Policy Behavior Typical use
  • Always (default) Restarts containers even when they exit successfully Web servers and long-running services
  • Never Never restarts containers One-off tasks where a restart would repeat work
  • On failure Restarts only when a container exits with an error Jobs that must complete successfully

If all containers exit and none restart, the container instance shuts down. A graceful shutdown timeout (default 0 seconds ) controls how long the instance waits for the operating system to shut down before powering off.

Storage Volumes

Volume type Purpose

File storage Persistent storage backed by OCI File Storage; the mount target must be reachable from the instance subnet

Empty directory A shared scratch directory for the containers, backed by memory (tmpfs) or ephemeral storage

Configuration file A Kubernetes-style volume containing one or more supplied files, such as configuration templates

Images and Registry Credentials

The registry that holds an image must be reachable from the instance's subnet:

For OCIR , use a subnet in a VCN with a service gateway .

For a public registry on the internet, use a public subnet with an internet gateway or a private subnet with a NAT gateway .

For private registries, registry credentials can be None , Basic (username and password), or an OCI Vault secret , which keeps the password out of the instance definition.

Container Security Settings

Each container can be hardened with a read-only root file system , run as non-root user , an explicit user ID and group ID, and Linux capabilities that you drop or add (for example, drop ALL and add only CAP_NET_BIND_SERVICE ).

Networking

A container instance gets a VNIC in the subnet you choose. Private subnets are recommended; a public IPv4 address can be assigned only in a public subnet. Network security groups control traffic to the instance, and a private DNS record can give it a stable hostname.

Lifecycle States and Billing

State Meaning Billed?

  • Creating Being created No
  • Active Running, or pulling images Yes
  • Updating Configuration change, restart, start, or stop in progress Yes
  • Failed Cannot be recovered, for example because an image could not be pulled No
  • Inactive Stopped by you, or all containers exited with restarts disabled No

Stopping a container instance pauses billing. Stopped and failed instances still count toward service limits. Container Instances also emits events (create, start, stop, restart, update, delete, maintenance) that you can route with Events rules.

Loading diagram... Choosing Where to Run a Container