Oracle Oracle AI Database@Azure Architect Professional 1z0-1147 Exam Dumps: Updated Questions & Answers (September 2026)

The requirements map directly to ZDM Physical Online Migration . A physical workflow uses RMAN-based database instantiation rather than Data Pump logical export/import. For online migration, ZDM combines physical target creation with Oracle Data Guard synchronization so redo generated after the initial database copy continues to be transported and applied to the target.

Because physical migration preserves the database at the block/file level, source and target compatibility requirements—including database version, platform characteristics, and character-set considerations—are more restrictive than with logical migration. The scenario explicitly states that the version and character set remain identical, which makes the physical workflow appropriate.

The online variant minimizes downtime because users continue operating against the source while target synchronization proceeds. Application interruption is concentrated around the final synchronization and switchover.

Logical Online instead uses Data Pump and GoldenGate. Physical Offline satisfies the RMAN requirement but introduces substantially longer downtime because the source cannot remain operational throughout migration.

Therefore, B is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Physical Online, RMAN and Data Guard.

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

The Data Guard Observer is an independent process used by Fast-Start Failover to monitor the primary and standby databases and determine whether an automatic failover should occur. Because its independence directly affects the reliability of the failover decision, it should not share the same failure domain as either database.

For an Oracle AI Database@Azure architecture spanning availability zones, placing the Observer on a separate Azure VM in another availability zone provides appropriate fault isolation. If the primary AZ fails, the Observer remains available to verify the failure and initiate the transition to the standby. Hosting the Observer directly on the primary database node would cause it to disappear with a primary-site outage. Hosting it on the standby similarly creates an undesirable dependency on the standby environment.

The Observer is an external Data Guard Broker process; it does not belong inside Oracle's multicloud control-plane Parent Site. For stronger resilience, Oracle Data Guard can also support multiple observers in appropriate configurations.

Therefore, D represents the recommended architecture.

Study Guide reference: HA and DR with Oracle AI Database@Azure — Data Guard Broker, FSFO and Observer placement.

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

Backup Retention Lock is a protection mechanism intended to prevent administrators or compromised credentials from prematurely reducing the recoverability window of Autonomous AI Database backups. Once the lock is established, normal administrative interfaces cannot simply disable it or reduce the protected backup-retention period.

Oracle's Autonomous AI Database documentation explicitly states that after the backup retention lock has been set, the option cannot be disabled or the retention period changed through ordinary database administration. To disable the lock or modify the locked retention setting, the administrator must file a Service Request with Oracle Cloud Support .

This design provides an administrative separation between ordinary database management and an action that could materially weaken backup protection. Changing an Azure Key Vault key has no relationship to the retention-policy lock. An SQL ALTER DATABASE command cannot override a service-level backup governance control, and the Azure Portal does not expose a supported bypass to reduce the locked period.

Accordingly, A is the only supported escalation path in the choices.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous AI Database backup protection, retention policy, retention lock and operational security controls.

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

This configuration is explicitly identified as unsupported in Microsoft's Oracle AI Database@Azure network-planning guidance. If two Oracle AI Database@Azure VNets are deployed in the same Oracle Availability Zone and one uses Advanced Networking while the other uses the default networking implementation, VNet peering between them can introduce asymmetric routing .

Asymmetric routing occurs when outbound and return traffic traverse different network paths. This is particularly problematic with stateful network elements and the differing routing models associated with the two Oracle AI Database@Azure network implementations. The result can be data-plane traffic loss toward the VNet using Advanced Networking.

VNet peering itself does not upgrade a previously provisioned VNet to Advanced Networking, nor does it downgrade the Advanced Networking environment. Advanced Networking capability is determined by the feature configuration and the state of the delegated subnet before Oracle resources/VNICs are provisioned.

Therefore, the two environments should not be directly peered in this mismatched state. The correct answer is A .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Advanced Networking compatibility and VNet peering.

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

Oracle AI Database@Azure exposes database and infrastructure metrics through Azure Monitor, but similarly named metrics correspond to different levels of the Oracle resource hierarchy. Correct interpretation of the label is therefore essential.

Oracle's monitoring documentation explicitly differentiates the namespaces. OCI Database Cluster represents VM-cluster-level measurements. OCI Database represents Container Database (CDB) metrics. Oracle OCI Database identifies Pluggable Database-level metrics. Consequently, to examine CPU utilization for an individual PDB, the administrator selects CPU Utilization (Oracle OCI Database) .

This distinction is particularly important for consolidated Exadata environments. A cluster-level CPU metric can show overall infrastructure utilization but cannot determine which PDB is responsible for a workload spike. Similarly, CDB-level utilization aggregates activity at the container-database layer. The Oracle OCI Database-labelled metric enables the administrator to work at the PDB scope needed for tenant or application-specific performance analysis.

The Azure Monitor integration therefore provides several metrics with superficially similar names, but their resource dimensions are deliberately different.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Azure Monitor integration, Exadata monitoring, VM Cluster/CDB/PDB metric scopes and operational observability.

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

Oracle's reference architecture for multi-region Oracle Database@Azure disaster recovery explicitly states that no subnet is required in the Hub VCN to enable transit routing .

The Hub VCN serves primarily as a routing construct connecting gateways and route-table attachments. DRGs, Local Peering Gateways, Remote Peering Connections, and VCN route tables provide the required network forwarding between the Oracle Database@Azure Child Site VCNs and remote regions. Because the hub does not need to host compute instances or network virtual appliances for this gateway-based transit model, it does not require a workload subnet.

This has an additional design benefit: the hub VCN can use a comparatively small CIDR range because there is no requirement to reserve substantial address space for servers or VNICs.

A public subnet and Internet Gateway are unnecessary because Data Guard traffic should traverse private cloud networking. Likewise, dedicated /24 transit-appliance subnets or per-availability-domain private subnets are not mandatory for the gateway-based topology.

Therefore, D is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — cross-region Data Guard, OCI Hub VCN and transit routing.

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

The two managed backup destinations represented in the question are OCI Object Storage and Oracle Database Autonomous Recovery Service .

OCI Object Storage is the established managed backup destination for Oracle Database services and stores Oracle-managed database backup objects in OCI. Autonomous Recovery Service is Oracle's recommended advanced database-protection platform. It provides database-aware incremental-forever backup processing, centralized protection policies, recoverability validation, retention locking, and optional real-time transaction protection.

For Oracle Database@Azure, Recovery Service can store protected-database backups either in the paired OCI region or, where supported and selected by policy, within the same Azure cloud provider location. Oracle architecture documentation therefore increasingly positions Autonomous Recovery Service as the preferred automatic-backup destination.

The physical Zero Data Loss Recovery Appliance is an on-premises engineered system rather than the managed cloud backup destination in this service. Direct Azure Blob Storage API access is likewise not presented as the standard built-in automatic Exadata backup destination; Azure-hosted Recovery Service storage is accessed through the managed Recovery Service architecture rather than direct customer Blob APIs.

Therefore, C and D are correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata backup destinations and Autonomous Recovery Service.

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

For ZDM physical online migrations using direct data transfer , Oracle's Maximum Availability Architecture pattern uses RMAN's Restore From Service capability. Rather than first creating backup pieces in a staging location, transporting them, and then restoring them on the target, RMAN restores the target database directly across the network from the source service.

This design reduces intermediate storage requirements and simplifies the migration pipeline. Once the target database has been instantiated, ZDM automatically configures Oracle Data Guard and uses redo transport to maintain synchronization until the planned switchover. The combination of Restore From Service and Data Guard is the central technical pattern Oracle documents for physical online migration to Exadata Database Service on Oracle AI Database@Azure.

Although DUPLICATE ... FROM ACTIVE DATABASE is a legitimate RMAN cloning capability in other contexts, it is not the named method documented for this ZDM direct-data-transfer workflow. Compressed backup-set streaming and incremental image-copy pushing also imply different backup/staging mechanisms.

Therefore, Restore From Service is the MAA-aligned RMAN method represented by the scenario.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — MAA, ZDM Physical Online migration, RMAN direct data transfer and Restore From Service.

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

During Exadata VM Cluster provisioning, the administrator selects the client delegated subnet and can explicitly provide a CIDR range for the Exadata backup network. If no backup-subnet CIDR is supplied, Oracle automatically uses the documented default of 192.168.252.0/22 .

The backup subnet serves Oracle database backup-network requirements and is architecturally distinct from the Azure delegated client subnet. Oracle's deployment-planning guidance emphasizes that the default backup CIDR is not part of the Azure VNet CIDR allocation. Nevertheless, address planning remains important. In disaster-recovery designs involving multiple Exadata deployments—especially cross-availability-zone or cross-region configurations—the administrator should explicitly choose non-overlapping backup CIDR blocks so that replication, routing, and backup traffic do not encounter conflicting address ranges.

Option B uses the correct network prefix but an incorrect /24 mask. Options A and D use different base networks and therefore do not match the Oracle provisioning default.

Accordingly, the correct response is C: 192.168.252.0/22 .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata VM Cluster client and backup networks, CIDR planning, default backup-subnet configuration and non-overlapping network design.

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

Oracle Database Autonomous Recovery Service supports Long-Term Retention (LTR) backups for organizations that need to preserve full database backups for compliance, regulatory, legal, or business requirements. The correct destination is the OCI Object Storage Infrequent Access tier .

The question source specifies that the LTR backup initially remains in the standard storage tier and transitions after the first 24 hours to Infrequent Access storage for the remainder of its retention period. Oracle's Recovery Service documentation independently confirms that long-term retention backups are stored in the Object Storage Infrequent Access tier and can be retained for periods extending up to ten years.

The Infrequent Access tier is appropriate because LTR backups are retained for extended periods but are generally restored less frequently than operational backups. Archive Storage is not the managed destination used by Recovery Service for this workflow. Azure Archive Blob Storage is likewise not the Oracle-managed OCI storage tier identified for these backups, and there is no "OCI Legacy Backup" storage tier.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous Recovery Service, LTR backups, retention and storage lifecycle.

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