Study guide
14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication
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
14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication
Key Takeaways Explain This Topic AI
Globally Distributed Autonomous AI Database runs on Autonomous AI Database on Dedicated Exadata Infrastructure and adds automated management of distributed database shards.
Each node of a Globally Distributed Autonomous AI Database is an independent database that stores a subset of the data, and nodes do not share storage.
The global service manager (GSM) routes each connection to the right node based on the sharding key, using its topology map of the distributed database.
Raft replication, available from Oracle AI Database 26ai, provides consensus-based replication with fast failover, zero data loss, and no reconfiguration when nodes are added or removed.
Globally Distributed Autonomous AI Database is billed by the number of ECPUs per hour.
Last updated: October 2026
When a Single Database Is Not Enough
A single Autonomous AI Database scales vertically and runs in one region, with standbys elsewhere for disaster recovery. Some applications need more:
Horizontal scale beyond what one database can handle, such as global payments, telecom, or IoT platforms with very high transaction volumes.
Data sovereignty , where customer data must physically stay in a specific country or region.
Data proximity , where users get lower latency because their data sits near them.
Fault isolation , where an outage affects only the subset of data on one node.
Oracle Globally Distributed Autonomous AI Database meets these needs by distributing one logical database across many nodes. Oracle describes it as a distributed version of Autonomous AI Database that runs on Autonomous AI Database on Dedicated Exadata Infrastructure and adds automated management of the distributed database. Applications still interact with a single logical database , and the service supports OLTP, analytics, and mixed workloads with relational, JSON, spatial, graph, and other data types.
Components
Component Role
Catalog A database that supports automated node deployment, centralized management, and multi-node queries . It stores the master copy of the schema and of duplicated tables, and acts as the multi-node query coordinator.
Node (shard) An independent database instance that stores a subset of the data . Nodes do not share storage , and they can be placed in one region or in different regions .
Data space In user-managed distribution, a node and its replica that store the data for a range or list of key values.
Global service manager (GSM) A regional listener that keeps a topology map of the distributed database and routes each connection to the correct node based on the sharding key .
Global service A database service that clients use to connect to the distributed database.
Sharding Keys, Sharded Tables, and Duplicated Tables
The sharding key is the column, such as customer_id or country_code , that decides which node stores a row.
Sharded tables are split across nodes by the sharding key.
A table family groups related sharded tables, such as customers, orders, and order lines, so that related rows live on the same node . Joins inside a family then run on one node without cross-node traffic.
Duplicated tables hold small reference data, such as product catalogs or currency codes, with a copy on every node so that joins with them also stay local.
When an application passes the sharding key while connecting, the GSM sends the connection directly to the node with that data, which is the fastest path. Queries without a sharding key, such as global reports, go through the catalog , which coordinates a multi-node query across the nodes.
Data Distribution Methods
Method How data is placed Best for
System-managed Rows are spread automatically by consistent hash of the sharding key, which balances data and load and avoids hot spots. Chunks are rebalanced automatically when nodes are added or removed. Scale-out with even distribution
User-managed (user-defined) You map ranges or lists of key values to specific data spaces , for example all EU customers to nodes in Frankfurt. Data sovereignty and data proximity
The underlying Oracle Globally Distributed AI Database also supports composite distribution, which combines user-defined groups with system-managed placement inside each group, and directory-based distribution, where a directory records each key's location. The distribution method and replication technology are fixed when the distributed database is created.
Replication: Data Guard or Raft
Replication How it works Notes
Oracle Data Guard (node level) Each primary node has physical standby nodes. Standbys can be in the same region for high availability or in another region for disaster recovery. Available with Oracle Database 19c and Oracle AI Database 26ai
Raft (chunk-set level) Data is divided into replication units, each with replicas on different nodes, and a consensus protocol keeps them in sync. Available from Oracle AI Database 26ai; fast failover with zero data loss; keeps the replication factor automatically when nodes fail; no reconfiguration when nodes are added or removed
For high availability, Raft-replicated nodes can be placed in different availability domains within a region. In the underlying database, Raft replication is supported only with the system-managed distribution method, and it does not protect the catalog, which can be protected with Data Guard.
Availability, Billing, and Limits
Oracle cites a 99.95% availability SLA, rising to 99.995% with Autonomous Data Guard.
Billing is based on ECPUs per hour , because the nodes and catalog are Autonomous AI Databases.
Service limits cover the number of distributed databases and distributed database private endpoints , plus the usual Autonomous AI Database limits for instances, ECPUs, and storage.
Connectivity uses a private endpoint in your VCN.
Design Example: A Global Payments Platform
A payments company must keep EU customer data in the EU and US customer data in the US, while handling millions of transactions per hour:
Use user-managed distribution with country_code as part of the sharding key, mapping EU values to data spaces in Frankfurt and US values to data spaces in Ashburn.
Put customers, accounts, and transactions in one table family so payment processing stays on one node.
Make currency and fee tables duplicated tables .
Protect each data space with replicas in another availability domain in the same region, so data does not leave its jurisdiction.
Run global finance reports through the catalog as multi-node queries.