1z0-1147 Exam Dumps : Oracle AI Database@Azure Architect Professional

Oracle Autonomous AI Database Serverless documents a local Autonomous Data Guard standby RTO SLO of two minutes for failure events that require failover to the standby.

For the Recovery Point Objective, current Oracle documentation is slightly more precise than the wording in option A: the local standby's maximum possible data-loss objective is less than 10 seconds . Therefore, the exam option stating "RPO of 10 seconds" represents the intended and closest supported value.

These SLOs apply to events such as full database failure, complete storage failure, corruption scenarios requiring standby transition, and availability-domain failures when Autonomous Data Guard is enabled. Local standby protection provides materially faster recovery and a substantially smaller possible data-loss window than cross-region standby protection because replication remains geographically close.

An hour-long RTO is inconsistent with active standby protection, while five-minute RPO and thirty-second RPO values do not match Oracle's stated local Autonomous Data Guard objectives.

Therefore, A is correct, interpreted technically as 2-minute RTO and < 10-second RPO .

Study Guide reference: HA and DR — Autonomous Data Guard local standby SLOs.

===============

Oracle's Hub-and-Spoke design guidance defines an important UDR rule for Oracle AI Database@Azure delegated subnets: the route prefix must be at least as specific as the delegated subnet CIDR . A /24 delegated subnet therefore cannot be reliably represented by a broader /16 route when the architecture requires the delegated subnet-specific path.

The less-specific route can fail to take precedence over more-specific system or service routes. This creates the possibility that traffic takes one route toward the database but returns through a different route. Such asymmetric routing is especially problematic with Azure Firewall or an NVA because stateful firewalls expect both directions of a connection to traverse the same inspection point. If the return packet follows a different path, the firewall can drop the session.

A UDR has no mechanism for duplicating VNICs, changing SQL*Net encryption, or resizing the underlying subnet. It simply influences Layer-3 forwarding.

Therefore, A accurately describes the documented routing consequence.

Study Guide reference: Configure Oracle AI Database@Azure Networking — UDR prefix specificity, delegated subnet routing, Hub-and-Spoke and asymmetric routing prevention.

===============

Oracle Zero Downtime Migration organizes its Oracle database migration methods into two fundamental workflow families: Physical Migration and Logical Migration . Each family can then have online and offline variants depending on compatibility requirements and acceptable downtime.

Physical migrations operate on the physical database representation and rely on technologies such as RMAN and Oracle Data Guard. Physical Online migration can instantiate a target using Restore From Service and maintain synchronization using Data Guard, while Physical Offline uses RMAN backup and restore.

Logical migrations operate through logical database objects and data. Oracle Data Pump provides the initial export/import mechanism, while Logical Online migration integrates Oracle GoldenGate to capture and replicate ongoing transactions before cutover. Logical workflows are also suitable for many cross-version or cross-platform scenarios that physical workflows cannot support.

"Container-based migration" and "snapshot-based migration" are not ZDM's top-level migration workflow categories.

Oracle's current ZDM documentation explicitly states that ZDM supports both Physical and Logical Migration workflows.

Therefore, B and D are correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM workflow categories.

===============