Study guide

2.2 OCI DNS Traffic Steering, Geolocation & Health Checks

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.2 OCI DNS Traffic Steering, Geolocation & Health Checks

Key Takeaways Explain This Topic AI

OCI Public DNS uses a global Anycast nameserver network paired with Traffic Management Steering Policies to route end-user requests dynamically across multiple cloud regions.

OCI Traffic Management offers five steering policy types: Failover, Load Balancer, Geolocation Steering, ASN Steering, and IP Prefix Steering.

Health Checks monitors test public endpoints over HTTP or ping protocols, and Oracle recommends at least three vantage points across three providers.

A Health Checks monitor with a 10-second test interval is classed as Premium; any longer interval is Basic.

Active-active multi-region architectures require distributed data synchronization and conflict resolution, whereas active-passive architectures leverage automated DNS failover to standby infrastructure.

Last updated: October 2026

OCI Global DNS and Anycast Architecture

Designing resilient, multi-region architectures requires managing ingress traffic before it reaches a specific data center or Virtual Cloud Network (VCN). OCI public DNS runs on a global anycast network, so the same nameserver addresses are announced from many locations and each query is answered by a nearby nameserver. This keeps lookups fast and spreads query load, which is why DNS-based traffic steering is the usual entry point for multi-region designs.

Beyond basic authoritative zone hosting, OCI provides Traffic Management Steering Policies . These policies dynamically alter DNS answers (such as A , AAAA , or CNAME records) based on endpoint health, client geographic location, network origin, or pre-configured load-balancing weights.

Traffic Management Steering Policies

OCI Traffic Management steering policies decide which answers the DNS service returns, based on endpoint health and the origin of the query. Oracle documents five policy types:

Failover : Answers are served in priority order, such as a primary in Ashburn and a secondary in Phoenix. Health Checks monitors evaluate the answers. If the primary answer is unhealthy, DNS traffic is automatically steered to the secondary.

Load Balancer : Traffic is spread across several endpoints using equal weights, or custom weights for ratio load balancing (for example, 70/30 during a gradual cutover). Unhealthy endpoints are removed, and traffic is redistributed to the healthy ones.

Geolocation Steering : Traffic is directed by the location of the end user, using regions defined by continent, country, or (in North America) state or province. Each geographic case can list answers in priority order, so an unhealthy regional endpoint is skipped and the next answer, such as a neighboring region, is served.

ASN Steering : Queries from a specific Autonomous System Number (ASN) , such as an enterprise network or a mobile operator, are steered to a chosen endpoint. A typical use is sending partner networks to dedicated resources.

IP Prefix Steering : Queries are steered by the IP prefix of the originating query, which is useful for giving internal and external users different answers.

Policy type Primary use case Routing decision Health awareness

Failover Active-passive disaster recovery Priority order (primary, then secondary) Health Checks monitors decide when to fail over

Load Balancer Active-active sharing, gradual cutover Equal or custom weights Unhealthy endpoints are removed from rotation

Geolocation Steering Data residency, regional latency Continent, country, or state/province of the user Unhealthy answers skipped within each case

ASN Steering Carrier or partner-specific routing Autonomous System Number of the query source Optional health evaluation

IP Prefix Steering Internal vs. external users IP prefix of the query source Optional health evaluation

Warning

OCI does not offer a "geoproximity" policy type. If an answer option relies on great-circle distance calculations, it describes a feature from another cloud provider.

OCI Health Checks: Monitors and Vantage Points

Steering policies use the Health Checks service to judge whether answers are healthy. Health Checks provides two tools:

Monitors continuously test public-facing endpoints. A monitor uses either the HTTP protocols (HTTP or HTTPS requests) or the ping protocols (ICMP or TCP connection tests).

On-demand probes run a one-time check through the REST API, limited by a credit allowance.

Key parameters and limits include:

Interval : A monitor with a 10-second test interval is classed as Premium. Longer intervals are Basic. The only difference between the two classes is how often the test runs.

Vantage points : Oracle maintains dozens of vantage points worldwide. Oracle recommends selecting three or more vantage points across three different providers , so a problem with one provider's network does not look like an outage of your application.

Scope : Health Checks tests public-facing endpoints. It cannot probe a private IP inside a VCN.

Limit : The service is limited to 1,000 endpoint tests per account.

Using several vantage points on independent providers is the main defense against false-positive failovers caused by a single transit network problem.

DNS TTL Considerations and Upstream Caching Mechanics

The effectiveness of automated DNS traffic steering depends on the Time-To-Live (TTL) configured on DNS records. TTL dictates the duration (in seconds) that intermediate recursive resolvers (such as corporate forwarders, public DNS resolvers like 8.8.8.8, and ISP DNS servers) cache the resolution response before issuing a new lookup to OCI Anycast nameservers.

Architectural tradeoffs of TTL values include:

Low TTL (30–60 seconds) : Essential for rapid disaster recovery failover. When the primary region fails and OCI DNS updates its steering response, client traffic shifts to the secondary region within 1 to 2 minutes.

High TTL (300+ seconds) : Minimizes DNS query volume and reduces network latency for repeat visitors, but delays failover; client browsers continue sending requests to the dead primary region until their local cache expires.

Recursive Resolver Clamping : Some public ISPs enforce minimum TTL overrides (e.g., 300 seconds), ignoring lower authoritative TTLs. Architects must account for this behavior when establishing realistic multi-region Recovery Time Objectives (RTO).

Multi-Region Patterns: Active-Active vs. Active-Passive

Enterprise architects must choose between two primary multi-region deployment topologies:

Active-Passive (Disaster Recovery) : Production traffic routes exclusively to the primary region. The secondary region maintains either a minimal "pilot light" environment or a fully pre-provisioned warm standby. Cross-region data replication maintains database and storage synchronization. A Failover steering policy redirects traffic only when catastrophic regional impairment occurs.

Active-Active (Global Load Sharing) : User traffic is actively served by two or more regions simultaneously via Geolocation Steering or weighted Load Balancer policies. This pattern eliminates failover delay and maximizes hardware utilization, but requires bidirectional database synchronization (e.g., OCI GoldenGate) and robust conflict-resolution mechanisms to prevent split-brain inconsistencies.

Loading diagram... OCI DNS Traffic Steering and Global Health Check Failover Flow