Study guide

13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity

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

13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity

Key Takeaways Explain This Topic AI

Autonomous AI Database supports four workload types: Lakehouse, Transaction Processing, JSON Database, and APEX Service.

Every Autonomous AI Database provides five predefined services (tpurgent, tp, high, medium, and low) for all workload types.

The tpurgent service has the highest priority and supports manual parallelism, while tp and low do not run with parallelism.

ECPUs are the billing metric for all new and existing Autonomous AI Database deployments, and OCPU is a retired legacy metric.

Autonomous AI Database on Dedicated Exadata Infrastructure is built from Exadata infrastructure, Autonomous Exadata VM Clusters, Autonomous Container Databases, and the databases inside them.

Last updated: October 2026

What "Autonomous" Means

Oracle Autonomous AI Database (formerly Autonomous Database) runs on Exadata infrastructure and automates the work that DBAs usually do by hand: provisioning, configuration, tuning, indexing, patching, backups, and scaling. You choose a workload type, the compute and storage size, and the network access; Oracle handles the rest. This is the main contrast with Base Database Service, where you decide when to patch and how to configure the database.

Workload Types

Workload type Product name Optimized for

Lakehouse Autonomous AI Lakehouse (formerly Autonomous Data Warehouse) Analytics: data marts, data lakes, and lakehouses

Transaction Processing Autonomous AI Transaction Processing Transactional, analytical, and batch workloads running concurrently

  • JSON Database Autonomous AI JSON Database JSON-centric document applications
  • APEX Service APEX Service Low-code application development with Oracle APEX

Pricing for compute and storage depends on the workload type selected. A database can be cloned to a different workload type when requirements change. For example, an Autonomous AI JSON Database is limited to 20 GB of data other than JSON documents, so an application that grows into relational tables can move to Transaction Processing.

Deployment Options

Option Infrastructure Who controls maintenance timing Typical use

Serverless Shared Exadata infrastructure managed by Oracle Oracle, within published maintenance windows (you can choose an Early or Regular patch level) Most applications; fast provisioning; pay per use

Dedicated Exadata Infrastructure Exadata infrastructure reserved for you in OCI You set maintenance schedules for the container databases Isolation requirements, many databases, custom maintenance windows

Exadata Cloud@Customer Dedicated Exadata in your data center You Data residency in your own facility

Autonomous AI Database on Dedicated Exadata Infrastructure has a layered structure:

Exadata infrastructure : the dedicated hardware.

Autonomous Exadata VM Cluster (AVMC) : a VM cluster carved from the infrastructure.

Autonomous Container Database (ACD) : holds maintenance settings, the database software version, and Autonomous Data Guard configuration for the databases inside it.

Autonomous AI Databases : the individual databases created by application teams.

Globally Distributed Autonomous AI Database (Chapter 14) also runs on dedicated Exadata infrastructure.

The ECPU Compute Model

ECPUs are the billing metric for all new and existing Autonomous AI Database deployments; OCPU is a retired legacy metric. You specify an ECPU count and storage when provisioning, and both can be changed later. Compute auto scaling, covered in the next section, lets the database use up to three times its ECPU count during peaks.

Provisioning Choices

When you create a database you choose:

Workload type and database version .

ECPU count and storage , and whether compute auto scaling (enabled by default) and storage auto scaling (disabled by default) are on.

Administrator password .

Network access : public endpoint, public endpoint with access control rules, or private endpoint.

License type : license included or bring your own license (BYOL); with BYOL Standard Edition, the ECPU count is limited to 32.

Patch level : Regular (default) or Early.

Predefined Database Services

Connections choose one of five predefined database services , available for every workload type . Each service has different priority, parallelism, and concurrency characteristics:

  • Service Priority Parallelism Best for
  • tpurgent Highest Supports manual parallelism Time-critical transactions
  • tp High (below tpurgent) No parallelism Typical transaction processing

high High priority for reporting and batch All operations run in parallel and are subject to queuing Low-concurrency analytics with few users

  • medium Medium Parallel; concurrency limit can be changed Moderate reporting and batch
  • low Lowest No parallelism Low-priority reporting, batch, and background work

Separating workloads by service protects interactive users. For example, route checkout transactions through tp or tpurgent and nightly reports through low or medium , so heavy queries queue instead of starving transactions. Enabling compute auto scaling changes the concurrency and parallelism settings of the predefined services. Within one session, the CS_SESSION package can switch to a different service.

Network Access

  • Option How it works When to use
  • Public endpoint, open Reachable from any IP with valid credentials Rarely appropriate for production

Public endpoint with access control list (ACL) Allows only listed IP addresses, CIDR blocks, or VCNs (traffic from a VCN through a service gateway) Controlled access without a private IP

Private endpoint The database gets a private IP in your subnet, with NSGs controlling access, and no public access Production systems, on-premises access over FastConnect or VPN

With a private endpoint, Oracle recommends a regional subnet for the best availability, and the same private endpoint applies to an Autonomous Data Guard standby after a failover or switchover.

Tools Included With the Database

Database Actions provides browser-based tools for SQL development, data loading, data modeling, and monitoring, and the database includes Oracle APEX and Oracle REST Data Services for building low-code applications and REST APIs.

Loading diagram... Dedicated Exadata Infrastructure Hierarchy