Study guide
4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
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.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
Key Takeaways Explain This Topic AI
An OCI DevOps project groups code repositories, build pipelines, deployment pipelines, artifacts, environments, and triggers.
Build pipelines run managed build stages defined by a build_spec.yaml file and can deliver images to OCIR and generic artifacts to Artifact Registry.
OCI DevOps supports blue-green and canary deployment strategies for both OKE and compute instance groups.
OKE blue-green and canary deployments require an NGINX ingress controller, while instance group blue-green and canary deployments shift traffic through a load balancer.
Canary deployments can roll back automatically to the last successful version if the production stage fails.
Last updated: October 2026
Why CI/CD Is on the Architect Exam
The cloud-native objective explicitly mentions "DevOps practices" with OKE, Container Instances, and the OCI DevOps service. An architect is expected to design a pipeline that builds, tests, scans, and releases services safely, with the ability to roll back quickly. OCI DevOps provides this as a managed service, so you do not maintain Jenkins servers or build agents.
DevOps Building Blocks
- Component Purpose
- Project Container for all DevOps resources of an application; sends notifications to an ONS topic
- Code repository Private Git repositories hosted by OCI DevOps
- External connection Link to GitHub, GitLab, or Bitbucket so their repositories can trigger builds
- Trigger Starts a build pipeline on events such as a push to a branch
- Build pipeline Stages that compile, test, and package code
Artifact A versioned reference to an output, such as a container image in OCIR, a Kubernetes manifest, a Helm chart, or a generic file in Artifact Registry
- Environment A deployment target: an OKE cluster, a compute instance group, or a Functions application
- Deployment pipeline Stages that release artifacts to environments
- Build Pipelines
A managed build stage runs on Oracle-managed build runners. Its instructions live in a build_spec.yaml file in the repository, which defines steps, environment variables, exported variables, and output artifacts. A typical build pipeline has these stages:
Managed build : compile, run unit tests, and build the container image.
Deliver artifacts : push the image to OCIR and upload other outputs, such as manifests, to Artifact Registry.
Trigger deployment : start the deployment pipeline with the new artifact versions.
The build pipeline runs with its own resource principal . You put build pipelines in a dynamic group and grant that group the access it needs, for example manage repos for OCIR and read secret-family to fetch credentials from Vault. Secrets are referenced from Vault in the build specification rather than stored in the repository.
Artifact Registry
Artifact Registry stores generic artifacts, such as JAR files, ZIP packages, or configuration bundles, in repositories. When you create a repository you can choose to make its artifacts immutable , so a published version cannot be overwritten. Container images belong in OCIR, not Artifact Registry.
Deployment Pipelines and Stages
A deployment pipeline is a graph of stages. Common stage types include:
Deploy to OKE using Kubernetes manifests, or deploy a Helm chart to OKE.
Deploy to an instance group of compute instances (rolling deployment).
Deploy to Functions by updating a function to a new image.
Invoke function to run custom checks.
Wait for a set time.
Manual approval , which pauses the release until an approver responds.
Shell stage for custom commands.
Strategy-specific stages: blue-green deployment and traffic shift , and canary deployment , canary traffic shift , and canary approval .
- Deployment Strategies
- Rolling Deployment
A rolling deployment updates instances or pods in batches. It needs no extra capacity, but old and new versions run side by side during the rollout, so the API and database schema must stay backward compatible. Rolling back means rolling out the previous version again.
Blue-Green Deployment
Two complete environments exist: blue (current production) and green (new release).
For instance groups , DevOps deploys the new version to the green instances and then shifts traffic on the load balancer from the blue backends to the green backends.
For OKE , you create two Kubernetes namespaces for the blue and green environments (the namespaces are selected in the stage, not written into the manifests), and an NGINX ingress controller routes traffic. The traffic shift stage switches the ingress so users reach the new namespace.
Rollback is fast: rerun the traffic shift stage manually to send traffic back to the untouched blue environment (blue-green pipelines do not support full pipeline redeployment). The tradeoff is running double capacity during the release window.
Canary Deployment
A small share of traffic goes to the new version first:
Canary deployment stage deploys the new version to a canary environment. For OKE this requires an NGINX ingress controller to route traffic; for instance groups you select a load balancer .
Canary traffic shift stage moves a defined percentage of traffic to the canary, optionally in several rounds.
Canary approval stage lets a person confirm that metrics and logs look healthy.
The production stage releases the new version everywhere.
You can enable automatic rollback to the last successful version if the production stage fails. Canary limits the blast radius of a bad release to a small group of users.
- Strategy Extra capacity Rollback speed Best for
- Rolling None Slow (redeploy old version) Internal services with compatible versions
Blue-green Double during release Fast (shift traffic back) Critical services needing instant cutover and rollback
- Canary Small canary environment Fast (stop the traffic shift) High-traffic services where risk must be limited
- Putting Security Into the Pipeline
A secure pipeline combines several services covered elsewhere in this guide: vulnerability scanning of images in OCIR, image signing with Vault keys and image verification on OKE, Vault secrets for credentials, manual approval stages for production, and Logging of every pipeline run for audit purposes.