Oracle Updated 1z0-1147 Exam Questions and Answers by sid

A Network Anchor provides the cross-cloud network integration context used by supported Oracle AI Database@Azure services, including important DNS-resolution capabilities between Azure and OCI .

For inbound DNS resolution toward Azure, Oracle's Network Control Plane can create an OCI forwarding DNS endpoint and associated forwarding rules. For Azure-to-OCI resolution, the service can create an OCI listening DNS endpoint and expose its address through the Network Anchor so Azure DNS infrastructure or on-premises DNS servers can forward queries for Oracle database namespaces.

When both directions are configured, the architecture provides bidirectional private DNS resolution between Azure and OCI environments. Network Anchors can also participate in private-zone synchronization depending on the database service and DNS configuration.

The Network Anchor is not a cryptographic key store; TDE keys belong in Oracle Wallet, OCI Vault, Oracle Key Vault, or Azure Key Vault. Nor does the Network Anchor create Azure Availability Zones/OCI Availability Domains or mandate an IPsec-only intercloud transport mechanism.

Therefore, B is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Network Anchors, DNS listening endpoints and forwarding endpoints.

For Oracle AI Database@Azure's documented Azure-to-OCI federation architecture, Microsoft Entra ID functions as the enterprise identity provider. Oracle's reference architecture explicitly states that Microsoft Entra ID provides federated identity and access management for Oracle AI Database@Azure.

The OCI IAM Identity Domain remains an essential component because it is the Oracle-side service provider and identity domain that trusts the Microsoft Entra identity provider. However, when the question asks which platform provides the federated corporate identity in the Azure-integrated architecture, the answer is Microsoft Entra ID.

Oracle's onboarding instructions configure an Oracle Cloud Infrastructure Console enterprise application in Entra ID and then configure the OCI identity domain with Microsoft Entra ID as its SAML identity provider. Administrators can subsequently use their corporate Entra credentials for SSO into OCI when Oracle-native management tasks require it.

AD FS represents an older on-premises Microsoft federation service, while Okta is a third-party identity platform rather than the natively documented Azure integration.

Therefore, A is correct.

Study Guide reference: Secure Oracle AI Database@Azure — Entra ID federation, OCI IAM Identity Domains and SSO.

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

For an Autonomous AI Database Serverless target, Oracle Zero Downtime Migration supports Logical Online and Logical Offline migration workflows.

Logical migration is necessary because Autonomous AI Database Serverless abstracts the underlying physical database infrastructure and does not expose the file-system and database-host control required for a conventional physical RMAN/Data Guard migration. ZDM therefore operates through logical database migration technologies.

Logical Offline uses Oracle Data Pump export and import to instantiate the target. Logical Online adds Oracle GoldenGate to the workflow so changes occurring on the source after the initial data load are captured and applied to the target until final cutover, greatly reducing application downtime.

Oracle's Oracle Database@Azure migration documentation explicitly lists these two workflows for migration to Autonomous Database Serverless. Physical Online and Physical Offline workflows apply to supported customer-managed Oracle database targets, such as Exadata Database Service, rather than Autonomous Serverless.

Therefore, A is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — Autonomous AI Database Serverless migration workflow support.

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

Oracle recommends OCI Full Stack Disaster Recovery (Full Stack DR) for orchestrating disaster-recovery operations around Oracle Database@Azure deployments.

Oracle's reference architecture for local and regional Oracle Database@Azure standbys explicitly recommends Full Stack DR to orchestrate database switchover and failover operations . The service can coordinate ordered disaster-recovery plans instead of requiring administrators to manually perform every database and infrastructure transition during an incident or DR drill.

Oracle Data Guard remains the underlying database replication and role-management technology, while Full Stack DR provides the higher-level orchestration framework for executing coordinated transitions.

Azure Site Recovery is primarily designed for Azure VM and workload replication/recovery and is not Oracle's recommended database-role orchestration service. GoldenGate provides logical replication and data integration rather than end-to-end DR orchestration. Azure Traffic Manager performs DNS-based traffic distribution and can participate in application routing, but it does not execute Oracle database switchovers or failovers.

Therefore, B is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — Full Stack DR orchestration and Data Guard role transitions.

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