1Z0-997-26 High Availability And Disaster Recovery Practice Questions

Explanation: Before creating a Data Guard association between two Oracle Base Database Systems in different OCI regions, the primary and standby VCNs must have network connectivity. In OCI, this is typically achieved with a Dynamic Routing Gateway (DRG) attached to each VCN and remote VCN peering (or an equivalent DRG-based connection) so that redo transport can flow between the regions. Without this connectivity, the broker cannot establish the association.

Explanation: Snapshot Standby is the only Data Guard mode that temporarily converts a physical standby into a fully read-write database for testing, then reverts it to a physical standby and discards the test changes. Because the primary keeps running and redo is still being received (just not applied while in snapshot mode), primary operations and RPO are unaffected. This makes it the canonical answer for 'DR drill in production without impacting the primary.'

Explanation: Data Guard provides role transitions (switchover/failover), Active Data Guard read-only offloading, and redo transport lag management.

Explanation: Option B is correct because Oracle Base Database Service provides automated backups that OCI manages and stores in Oracle-managed Object Storage, with no customer bucket configuration required. Option C is correct because you can trigger on-demand manual backups through the OCI Console, CLI, or API, and these backups are written to Object Storage. Option D is correct because RMAN is the native Oracle backup and recovery tool and can be run directly against the database to create backups. Option A is not a supported backup method: copying datafiles with scp while the database is open in read-write mode without RMAN produces inconsistent, unusable backups. Option E is not valid because exporting database files to a Block Volume configured as a swap file is not a supported OCI backup mechanism and would not yield a recoverable backup.

Explanation: Geolocation steering (B) is correct because it routes clients to the closest or designated regional endpoint based on their geographic location, which is a common DR pattern for directing users to a healthy primary or secondary region. Failover steering (C) is correct because it actively monitors the primary endpoint with health checks and automatically redirects DNS answers to the secondary region when the primary fails, which is the core mechanism of DNS-based disaster recovery. Load Balancer steering (E) is correct because it distributes traffic across multiple endpoints using weighted distribution, allowing administrators to shift traffic proportions between primary and secondary regions during DR events. Round-robin routing through a single static IP without health checks (A) is not appropriate because it cannot detect a failed region and provides no failover capability. Manual BGP hijacking between VCN subnets (D) is not a valid OCI DNS Traffic Management steering method; BGP route manipulation is not how OCI steering policies operate.