Study guide
3.3 DR Drills, Plan Customization & Operational Readiness
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
3.3 DR Drills, Plan Customization & Operational Readiness
Key Takeaways Explain This Topic AI
A Start Drill execution creates a replica of the application stack in the standby DR protection group, and a Stop Drill execution terminates that replica.
For Base Database and Exadata Database members, Start Drill converts the standby database to a snapshot standby, and Stop Drill converts it back to a physical standby.
For Autonomous AI Database Serverless members, a drill uses either a snapshot standby or a clone or refreshable clone, depending on the member setting.
User-defined steps can run a script from Object Storage, run a local script on an instance through the Oracle Cloud Agent, or invoke an OCI Function.
While the protection groups are in the drill-in-progress state, only a Stop Drill plan can be executed.
Last updated: October 2026
Why Drills Matter
Regulators and auditors increasingly expect evidence that disaster recovery works, not just a written plan. Traditional DR tests often required breaking replication or scheduling downtime. Full Stack DR provides two plan types for testing: Start Drill and Stop Drill . A drill brings up a replica of the application in the standby region while production keeps running and replication continues.
What a Drill Does to Each Member Type
Full Stack DR generates built-in drill steps from the members of the protection groups:
Member type Start Drill Stop Drill
Moving compute instance Launches the instance in the standby region Stops and terminates the drill instance and removes it from the DRPG
Non-moving compute instance Starts the standby instance and attaches block volumes if configured Detaches the block volumes and stops the instance
Volume group Restores the volume group in the standby region from its replica or backup Terminates the restored volume group
Base DB / Exadata database Converts the standby to a snapshot standby Converts it back to a physical standby
Autonomous Container Database Converts the standby to a snapshot standby Converts it back to a physical standby
Autonomous AI Database Serverless Converts the cross-region standby to a snapshot standby, or creates a clone or refreshable clone Converts back to physical standby, or deletes the clone
MySQL HeatWave DB system Built-in Start Drill steps Built-in Stop Drill steps
A snapshot standby is a standby database opened read-write for testing. It keeps receiving redo from the primary but does not apply it until it is converted back, at which point the test changes are discarded and the standby catches up. Production replication is therefore never broken by the drill.
While the protection groups show a drill in progress state, the only plan you can execute is Stop Drill . You cannot start a switchover or failover until the drill is cleaned up, so always finish drills promptly.
Keeping the Drill Isolated
The biggest risk in a drill is a test copy that talks to production. Practical controls include:
Separate drill networking. When you add a moving instance, you define VNIC mappings to destination subnets. Point drill traffic at subnets whose route tables and security rules do not reach production systems or on-premises networks.
Separate DNS and connection strings. Make sure drill instances resolve test database endpoints, not the production primary.
No production traffic. Do not add drill instances to production load balancer backend sets. Test through a private endpoint or a separate listener.
Least privilege. The resource principal that Full Stack DR uses should only reach the compartments involved in the plan.
Extending Plans with User-Defined Steps
Infrastructure recovery is only half the job. Applications often need startup ordering, configuration changes, and smoke tests. Full Stack DR supports three kinds of user-defined steps:
Step type How it runs Typical use
Run Object Storage script Downloads a script from a bucket and runs it on an instance Centrally managed scripts reused by many plans
Run local script Runs a script already on the instance through the Oracle Cloud Agent Run Command plugin Mount file systems, update configuration, start services
Invoke Function Calls an OCI Function Control-plane tasks such as updating a DNS steering policy or calling an ITSM webhook
Run Command works through the Oracle Cloud Agent's outbound connection, so you do not need to open inbound SSH or create a bastion session for drill instances. The instance must have the Compute Instance Run Command plugin enabled, and Full Stack DR's dynamic group needs permissions such as manage instance-agent-command-family . Functions invoked from a plan need read fn-app , read fn-function , and use fn-invocation permissions for the Full Stack DR dynamic group, and a synchronous function call can run for at most 300 seconds.
You can also add a pause group , which stops the plan at a chosen point until an operator resumes it. This is useful when a manual verification, such as a business user checking a report, must happen before traffic is redirected.
Evidence for Auditors
A drill is only useful for compliance if you can show what happened:
Plan execution history in the Console shows each group and step, its status, and its duration.
Operation logs are written to the Object Storage log location configured for Full Stack DR, including output from user-defined scripts.
OCI Audit records every Full Stack DR API call, such as creating plans and launching executions. Audit logs are retained for 365 days.
Events from Full Stack DR resources can trigger notifications when an execution starts, fails, or completes.
Measure the elapsed time of each drill against your RTO target, and compare the database and storage recovery points against your RPO. Repeating the drill after every major architecture change keeps the plan aligned with reality.
Drill Checklist
Run prechecks on the Start Drill plan.
Execute Start Drill and confirm that every group succeeds.
Test the application through isolated endpoints.
Record timings and results.
Execute Stop Drill to remove the replica and return databases to physical standby.
Fix any failed steps and refresh the plans if members changed.