Study guide
1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
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
1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
Key Takeaways Explain This Topic AI
Oracle's Well-Architected Framework for OCI has five pillars: security and compliance, reliability and resilience, performance and cost optimization, operational efficiency, and distributed cloud.
The reliability and resilience pillar covers scalability, service limits and quotas, fault-tolerant networking, health checks, data backup, data replication, and disaster recovery.
Light in fiber travels roughly 200 km per millisecond, so each 100 km of distance adds about 1 ms of round-trip time to synchronous commits.
Cloud Advisor analyzes a tenancy's resources once a day and recommends cost management, performance, and high availability improvements.
Last updated: October 2026
Why a Framework Matters on This Exam
Professional questions rarely ask "what does this service do?" They ask which design best satisfies a set of business constraints. Oracle's Well-Architected Framework for Oracle Cloud Infrastructure gives a structured way to evaluate those designs. Learning its five pillars helps you recognize which constraint a question is really testing: security, recoverability, cost, operations, or data location.
The Five Pillars
Oracle's framework (published in the Oracle Architecture Center as "Learn About the Well-Architected Framework for Oracle Cloud Infrastructure") defines the pillars and their focus areas as follows.
Pillar Goal Key focus areas
Security and compliance Secure and protect systems and information assets User authentication and authorization; resource isolation and access control; database security; data protection; network security; monitoring and auditing; optimizing security posture
Reliability and resilience Build reliable applications on resilient infrastructure Scalability; service limits and quotas; fault-tolerant network architecture; health checks; data backup; data replication; disaster recovery
Performance and cost optimization Use resources efficiently for the best performance at the lowest cost Compute sizing; storage strategy; network monitoring and tuning; cost tracking and management
Operational efficiency Operate and monitor applications to deliver maximum business value Deployment strategy; workload monitoring; OS management; operations support
Distributed cloud Place and run workloads across environments Workload placement; integration across environments; compliance and sovereignty; resilience and DR; unified operations
Notice that Oracle combines performance and cost into one pillar. This is different from some other cloud frameworks, so be careful with distractors that list "operational excellence" or a separate "cost optimization" pillar as Oracle terms.
Mapping the Pillars to the Exam Objectives
Exam objective Pillars it draws on most Example services
HA and DR (15%) Reliability and resilience Fault domains, load balancers, block volume replication, Full Stack DR
Cloud-native (20%) Operational efficiency; performance and cost OKE, Container Instances, Functions, DevOps, Resource Manager
Security (25%) Security and compliance IAM, Cloud Guard, Security Zones, Bastion, ZPR, Network Firewall, WAF, Vault
Databases (20%) Reliability; performance and cost Base Database, Autonomous AI Database, Recovery Service, OCI Cache
Observability (20%) Operational efficiency; security monitoring Monitoring, Alarms, Logging, Audit, Connector Hub
The shared responsibility model also runs through every pillar. Oracle secures the physical facilities, hardware, and the managed service control planes. You remain responsible for identities, policies, network rules, data classification, encryption key choices, and the guest operating system of compute instances you manage.
Tradeoff 1: Synchronous vs. Asynchronous Replication
Light in optical fiber travels at roughly 200,000 km per second, which is about 200 km per millisecond. A request and its acknowledgement must make the trip twice, so every 100 km adds about 1 ms of round-trip time before routing and processing overhead.
Synchronous replication waits for the remote copy to confirm each write. It can deliver an RPO of zero, but distance adds latency to every commit.
Asynchronous replication confirms writes locally and ships changes in the background. Performance is not tied to distance, but a sudden failure can lose the changes still in flight.
Worked example: two regions 1,200 km apart add about 12 ms of propagation delay to every synchronous commit, before any network or database overhead. For a transaction that issues many commits, that delay adds up quickly. The usual OCI pattern is therefore synchronous protection inside a region (for example, an Autonomous Data Guard local standby in another availability domain or fault domain) combined with asynchronous protection to a remote region.
Tradeoff 2: Static Capacity vs. Elasticity
Static overprovisioning absorbs spikes instantly but pays for idle capacity. Elastic designs, such as instance pool autoscaling, OKE cluster autoscaling, or Autonomous AI Database compute auto scaling, reduce waste but need time or headroom to react. OCI instance pool metric autoscaling, for example, acts only after three consecutive one-minute averages breach the threshold. Predictable peaks are better handled with schedule-based scaling than with metrics alone.
Tradeoff 3: Centralized vs. Distributed Inspection
Routing all north-south and east-west traffic through a central Network Firewall simplifies policy and logging but adds a routing hop and requires careful, symmetric route tables. Distributed controls such as network security groups (NSGs) and ZPR policies enforce rules close to the workload without a central choke point. Many architectures combine both: NSGs and ZPR for segmentation, plus a firewall for deep inspection of traffic that leaves trusted zones.
Tradeoff 4: Managed Services vs. Self-Managed Components
A recurring exam theme is choosing the managed option that meets requirements with the least operational effort. Full Stack DR replaces hand-written failover runbooks, Bastion replaces public jump hosts, Vault replaces secrets stored in files, and Autonomous AI Database replaces manual patching and tuning. When two options meet the technical requirement, the one with lower operational overhead and fewer custom scripts is usually correct.
Cloud Advisor: The Framework in Daily Practice
Cloud Advisor analyzes all resources in a tenancy once a day. It flags cost-saving opportunities, performance bottlenecks, and availability issues, and shows the potential savings for each recommendation. Typical cost management findings include underutilized compute instances, overprovisioned Autonomous AI Lakehouse instances, unattached block and boot volumes, and Object Storage buckets without lifecycle policy rules. Access to Cloud Advisor is controlled with the optimizer-api-family resource type in IAM policies.
Cloud Advisor recommends; it does not enforce. To prevent risky configurations you use Security Zones, and to detect and respond to security problems you use Cloud Guard. Both are covered in Chapter 10.