Oracle AI Database@Azure Architect Professional 1z0-1147 Exam Questions with Experts Answers Updated Recently

Oracle's current network guidance defines two important delegated-subnet constraints. First, each Azure VNet can contain a maximum of one Oracle AI Database@Azure delegated subnet . Second, a single delegated subnet can support multiple VM Clusters , provided IP capacity and availability-zone constraints are satisfied.

Oracle clarifies that multiple VM Clusters from the same Exadata Infrastructure can share a delegated subnet. VM Clusters belonging to different Exadata Infrastructure resources can also share one when those infrastructure resources reside in the same availability zone .

However, Exadata Infrastructure resources located in different availability zones cannot share the same delegated subnet. Oracle identifies such a configuration as producing a suboptimal network path and requires separate delegated networking for cross-zone deployments.

The delegated subnet also uses Azure private address space; it is not required to use—and should not be designed around—a public IPv4 CIDR range.

Therefore, A and C are correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated-subnet limits, VM Cluster placement and IP addressing.

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

Oracle AI Database@Azure integrates its operational telemetry with Azure Monitor diagnostic settings so organizations can apply existing Azure observability, compliance, and SIEM architectures to Oracle database infrastructure.

Three standard destinations are relevant here. An Azure Log Analytics workspace receives telemetry for centralized querying, dashboarding, alerting, and Kusto Query Language analysis. An Azure Storage account can archive logs or metrics for retention, compliance, or later processing. Azure Event Hubs provides a streaming destination for forwarding telemetry to SIEM products, custom consumers, event-processing pipelines, or other downstream platforms.

Oracle's Oracle AI Database@Azure monitoring documentation specifically lists Log Analytics Workspace, Storage Account, and Event Hub among the available Azure Monitor diagnostic-routing destinations. Oracle Enterprise Manager can monitor Oracle environments but is not an Azure Monitor diagnostic-settings destination. OCI Object Storage is likewise not selected directly as a destination from the Azure diagnostic-settings workflow. Azure SQL Database is a database service rather than a supported diagnostic sink.

Therefore, the three correct selections are A, C, and D .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — monitoring, Azure diagnostic settings, Log Analytics, Storage accounts and Event Hubs.

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

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.

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