Study guide
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers
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
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers
Key Takeaways Explain This Topic AI
Availability Domains (ADs) represent physically isolated data centers within a region, while Fault Domains (FDs) provide hardware, rack, switch, and power anti-affinity boundaries inside an AD.
In single-AD regions, high availability relies on spreading instances across FAULT-DOMAIN-1, FAULT-DOMAIN-2, and FAULT-DOMAIN-3, because each fault domain has separate hardware.
Instance pools create identical instances from an instance configuration and can automatically register new instances in an attached load balancer's backend set.
Metric-based autoscaling fires after three consecutive one-minute averages breach a threshold, and its cooldown has a 300-second minimum and default.
Load balancer health checks default to a 10,000 ms interval, a 3,000 ms timeout, and 3 retries before a backend is taken out of rotation.
Last updated: October 2026
Regional Architecture: Availability Domains and Fault Domains
Designing resilient cloud infrastructure begins with understanding the physical and logical boundaries of Oracle Cloud Infrastructure (OCI). An OCI Region is a localized geographic area containing one or more Availability Domains (ADs) . Certain heritage regions (such as US East Ashburn, US West Phoenix, Germany Central Frankfurt, and UK South London) feature three Availability Domains connected by a private, high-speed, low-latency fiber network. Most newer expansion regions are single-AD regions , designed for rapid geographic footprint deployment while delivering enterprise-grade redundancy within a single metropolitan data center facility.
To ensure resilience within an individual Availability Domain, OCI partitions every AD into three Fault Domains (FDs) : FAULT-DOMAIN-1 , FAULT-DOMAIN-2 , and FAULT-DOMAIN-3 . A Fault Domain represents a logical grouping of physical hardware, including distinct physical server racks, redundant power distribution units (PDUs), uninterruptible power supplies (UPS), and dedicated top-of-rack (TOR) network switches. Fault Domains share no single point of hardware failure within the AD.
Fault Domains serve two critical architectural functions:
Hardware failure mitigation : If a physical server hypervisor crashes, a rack PDU trips, or a network switch fails, only compute and database nodes situated within that specific Fault Domain are impacted.
Maintenance isolation : A hardware failure or Compute hardware maintenance event that affects one Fault Domain does not affect instances placed in the other Fault Domains, so spreading replicas across all three keeps the service running during host maintenance.
Single-AD vs. Multi-AD High Availability Strategies
Architects must structure workloads differently depending on regional topology:
Multi-AD Regions : High availability can be achieved across data centers. An active-active compute tier distributes web and application nodes across AD-1 , AD-2 , and AD-3 . Database architectures can deploy an active primary database in AD-1 and a synchronous standby replica in AD-2 using Data Guard, eliminating data center facility loss as a catastrophic failure mode.
Single-AD Regions : High availability is achieved by enforcing anti-affinity across FD-1 , FD-2 , and FD-3 . Workloads must never place all application nodes or database replicas in the same Fault Domain. For instance, a two-node Oracle Real Application Clusters (RAC) system or primary-standby database pair allocates Node 1 to FD-1 and Node 2 to FD-2 , achieving hardware and power separation within the same data center.
Architecture Tier Multi-AD Region Deployment Single-AD Region Deployment Failure Mitigation
Web / Presentation Regional Load Balancer routing to VMs across AD1, AD2, AD3 Regional Load Balancer routing to VMs across FD1, FD2, FD3 Hypervisor, rack, or facility loss
Application / Logic Instance Pool distributed across all 3 ADs and FDs Instance Pool distributed across FD1, FD2, and FD3 Server crash, TOR switch failure
Database / State RAC nodes in different FDs of one AD, plus a Data Guard standby in another AD 2-node RAC across distinct FDs, plus a standby in another FD or region Node, rack, or data center loss
Storage Replication Cross-AD block volume or volume group replication Volume backups and cross-region replication (cross-AD replication needs a multi-AD region) Storage server or data center loss
Instance Configurations and Instance Pools
To build self-healing, horizontally scalable compute clusters, enterprise architectures pair Instance Configurations with Instance Pools :
Instance Configuration : An immutable template defining compute parameters, including base OS image (custom or platform), compute shape (bare metal, standard VM, or flexible VM with defined OCPU and memory allocations), Virtual Network Interface Card (VNIC) attributes, subnet attachments, cloud-init initialization scripts, storage volume attachments, and tags.
Instance Pool : A group of instances created from one instance configuration and managed together (create, start, stop, terminate, and resize). Placement configurations spread the pool across availability domains and fault domains. When a load balancer or network load balancer is attached, every instance added to the pool is automatically added to the backend set and starts receiving traffic once it passes the health check.
Autoscaling Policies: Metric-Based vs. Schedule-Based
Instance pools integrate with Autoscaling Policies to respond dynamically to load demands without manual operator intervention:
Metric-Based Autoscaling : Evaluates aggregated performance metrics emitted by the OCI Monitoring service. Typical trigger metrics include CPU utilization and memory utilization. The architect configures:
Scale-Out Rule : Metrics are aggregated into one-minute periods and averaged across all instances in the pool. When three consecutive one-minute averages meet the threshold (for example, average CPU above 75%), autoscaling adds a defined number of instances, up to the configured maximum pool size.
Scale-In Rule : When three consecutive one-minute averages fall below the scale-in threshold (for example, average CPU below 25%), autoscaling removes a defined number of instances, down to the configured minimum pool size.
Cooldown Period : The minimum time between metric-based scaling events. The minimum value is 300 seconds , which is also the default, and the cooldown starts when the pool returns to the Running state. A longer cooldown and a wide gap between the scale-out and scale-in thresholds prevent autoscaling thrashing (adding and then quickly removing instances).
Schedule-Based Autoscaling : Uses Quartz cron expressions to set a target pool size, or to stop and start the pool's instances, at known times such as business-hour surges or nightly batch windows. One autoscaling configuration holds either a single metric-based policy or up to 50 schedule-based policies.
Regional Load Balancers and Health Check Probe Tuning
The OCI Load Balancer service is the usual single ingress point for highly available architectures. A load balancer is a regional resource built from a primary and a standby node placed in separate availability domains (multi-AD regions) or separate fault domains (single-AD regions). If the primary node fails, the standby takes over the same IP address, so clients do not need a DNS change.
Traffic is forwarded to backend sets populated by instance pool members. Ensuring traffic reaches only healthy instances requires precise health check probe tuning:
Protocol : TCP-level checks (a TCP handshake) or HTTP-level checks (a request to a URI), optionally using SSL.
Path : A dedicated lightweight health endpoint (such as /healthz or /status ), decoupled from deep computational database queries to avoid false degradation during heavy load.
Interval : Frequency of health checks (default 10,000 milliseconds).
Timeout : Maximum wait for a backend response (default 3,000 milliseconds).
Retries : The number of failed checks before a backend is taken out of rotation (default 3). A backend that later passes the health check is returned to rotation automatically.
Response validation : HTTP checks validate the returned status code (for example, 200 ) and can match the response body with a regular expression.
Loading diagram... High Availability Compute and Database Architecture Across Fault Domains and Availability Domains