Oracle Updated 1z0-1147 Exam Questions and Answers by harper-rose

Oracle documents multiple Azure network patterns for application connectivity to Oracle AI Database@Azure, including VNet peering and Hub-and-Spoke VNet peering .

VNet peering enables application workloads in one Azure VNet to communicate privately with Oracle database resources exposed through a delegated subnet in another VNet. This is appropriate when relatively direct, low-latency communication is required.

A Hub-and-Spoke design introduces a central hub containing shared connectivity and security services, such as Azure Firewall, a Network Virtual Appliance, ExpressRoute gateway, or VPN gateway. Application and database VNets connect as spokes or workload/data networks, allowing centralized inspection and hybrid connectivity.

Oracle's documented topology set also includes local VNet, global connectivity, on-premises Hub-and-Spoke, and related enterprise designs. A point-to-site VPN client model is not identified as the standard application topology requested here. More fundamentally, an Oracle AI Database@Azure deployment cannot exist without an Azure VNet and delegated networking.

Therefore, the correct selections are B and C .

Study Guide reference: Configure Oracle AI Database@Azure Networking — VNet Peering and Hub-and-Spoke topologies.

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

Among the choices presented, Oracle Exadata Database Service on Dedicated Infrastructure and Oracle Autonomous AI Database are both native Oracle AI Database@Azure database services designed to run on Oracle-optimized database infrastructure located inside Azure data centers. Exadata Database Service provides customer-managed Oracle Database environments on purpose-built Exadata hardware, with RAC, Data Guard, elastic compute, and high-performance storage capabilities. Autonomous AI Database provides a fully managed database model in which Oracle automates provisioning, patching, tuning, backup operations, and resource scaling.

Oracle's current service portfolio has expanded further and now also includes Exadata Database Service on Exascale Infrastructure, Base Database Service, Autonomous AI Database on Dedicated Exadata Infrastructure, GoldenGate, and Autonomous Recovery Service. However, those services are not alternatives in this question. Oracle NoSQL Database Cloud Service is not one of the listed Oracle AI Database@Azure database offerings, while a generic Oracle Database Standard Edition VM running on Azure IaaS is not equivalent to a native Oracle AI Database@Azure service.

Therefore, B and C are correct. Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — supported database services and optimized Oracle infrastructure.

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

Purchasing the Azure Marketplace offer establishes the commercial entitlement, but it does not by itself establish the technical relationship between the customer's Azure environment and OCI tenancy. Oracle's onboarding sequence requires multicloud linking after purchase.

During this step, the selected Azure subscription is linked with an Oracle Cloud Infrastructure tenancy. That association enables the service to establish the required cross-cloud resource, subscription, governance, and management relationships. Oracle's current overview explicitly states that after the purchase is complete, the Azure subscription is linked with an OCI tenancy; this process is called multicloud linking.

Only after onboarding and linking are completed does the administrator move into resource provisioning. At that stage, the environment can be prepared with the VNet, delegated subnet, Exadata infrastructure, VM Cluster, Autonomous AI Database, or applicable anchor constructs. Therefore, creating networking components before completing the required subscription/tenancy association reverses the documented onboarding sequence.

DNS-specific configuration is also part of networking rather than the immediate post-purchase account-linking requirement.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Marketplace purchase, multicloud linking, Azure subscription-to-OCI tenancy association and provisioning prerequisites.

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

When Oracle Autonomous AI Database Serverless is provisioned through Oracle AI Database@Azure, the administrative database account follows the standard Autonomous Database account model. The Azure creation workflow exposes the Username field as read-only and set to ADMIN .

The administrator therefore supplies the password for the predefined ADMIN account but does not choose or rename the account during database creation. Oracle currently specifies password requirements separately, including minimum and maximum length and character-composition requirements.

The account is not derived from the Microsoft Entra ID identity that deploys the Azure resource. Azure RBAC and Microsoft Entra authentication govern access to the Azure resource-management plane, whereas the ADMIN credential is a database-level account. Similarly, SYS is not presented as the configurable provisioning username for Autonomous AI Database Serverless, and the username is not generated from subscription metadata.

This separation between Azure control-plane identity and Oracle database credentials is architecturally important when designing authentication and administrative access.

Therefore, the correct answer is A .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database Serverless creation, configuration and administrator credentials.

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