1z0-1147 Oracle AI Database@Azure Architect Professional Questions and Answers

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.

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

The correct solution combines Oracle Database Autonomous Recovery Service Long-Term Retention (LTR) with Retention Lock .

Recovery Service permits an LTR backup to be retained for up to 3,650 days—10 years . LTR backups are independent of the normal operational backup window and are designed specifically for compliance, regulatory, legal, and archival requirements.

Retention Lock adds the required immutability control. Oracle describes Retention Lock as an enforcement mechanism that protects retained backups against inadvertent changes and malicious actions such as ransomware. Once governed by the locked protection policy, backup retention cannot simply be shortened or deleted through normal backup-administration privileges before the protected period expires.

A 60-day Object Storage policy fails the ten-year requirement. Manual NFS backups lack the managed LTR and retention-lock framework, while Data Guard standby databases solve availability and disaster-recovery problems rather than replacing governed backup retention.

Therefore, C uniquely satisfies both long-term retention and immutability.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Recovery Service, LTR and Retention Lock.

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

The foundational Exadata configuration is constructed from two distinct server tiers: database servers that execute Oracle Database workloads and Exadata Storage Servers that provide intelligent, scale-out database storage. Oracle's Exadata technical architecture identifies the base configuration as two database servers and three storage servers .

Two database servers provide the minimum database compute topology necessary for the architecture's availability and clustered database capabilities. A single database server would eliminate the server-level redundancy expected from the standard Exadata infrastructure design. On the storage side, three Exadata Storage Servers form the baseline storage configuration and support the redundancy mechanisms used by Oracle Automatic Storage Management and Exadata storage services.

Oracle documents the same two-database-server/three-storage-server starting configuration across current Exadata architectural material. Additional database or storage servers can be added in supported elastic configurations, but those expansions do not alter the minimum starting configuration asked for in the question.

Therefore, B and D are correct. Two storage servers are below the supported storage-server baseline, while one database server does not constitute the standard Exadata base infrastructure.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata Infrastructure architecture, database servers, storage servers, infrastructure sizing.

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

Oracle AI Database@Azure applies a regional service limit to delegated subnet usage. The documented default is five delegated subnets per OCI tenancy in a specific region . This is a service quota rather than a limitation that can be bypassed through additional Azure routing constructs.

To exceed the default, the customer must request a service limit increase . Oracle identifies the relevant OCI service as Multicloud, the resource as Delegated Subnet Multicloud Links , and the corresponding service-limit name as azure-delegated-subnet-count. The limit is regional, so introducing another VNet, Route Server, VNet peering relationship, or Microsoft Entra tenant does not increase the permitted count.

Current documentation phrases the operation as requesting a service limit increase through Oracle's service-limit process. Among the supplied choices, option D is the only one that represents that required Oracle-side quota increase.

Architecturally, this distinction matters because routing topology and service capacity are independent control planes: networking objects determine reachability, whereas Oracle-enforced service limits determine how many delegated-subnet links may exist.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet limits and Multicloud service-limit management.

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

Oracle's current Oracle AI Database@Azure service matrix explicitly identifies Oracle Exadata Database Service on Exascale Infrastructure as eligible for both Private Offer and Public Offer purchasing models.

A Public Offer uses a pay-as-you-go Azure Marketplace model and allows customers to begin consuming supported services without first negotiating a custom contract with Oracle Sales. A Private Offer is based on negotiated commercial terms and is appropriate for enterprise commitments and customized pricing.

Exadata Database Service on Dedicated Infrastructure is Private Offer eligible but not Public Offer eligible. The same Private-Offer-only restriction applies to Autonomous AI Database on Dedicated Exadata Infrastructure. Oracle Database Autonomous Recovery Service is a database protection service rather than the alternative primary high-performance Exadata database platform requested by the scenario, and it is also listed as Private Offer only.

Exascale therefore combines Exadata database capabilities with a lower-entry, elastic shared-infrastructure model and marketplace flexibility.

Thus, A is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Azure Marketplace offers and available database services.

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

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.

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

Oracle AI Database@Azure depends on Azure Resource Manager provider namespaces that expose the Oracle service and its underlying infrastructure integration. Among the listed choices, the required providers are Microsoft.BareMetal and Oracle.Database .

Oracle.Database is the Azure resource-provider namespace through which Oracle database multicloud resources are represented and managed in Azure. This includes Oracle AI Database@Azure database-resource lifecycle operations and integration with delegated networking. Microsoft.BareMetal supports the Azure-side integration with specialized Oracle infrastructure physically deployed within Azure facilities.

Current Microsoft onboarding documentation also lists Microsoft.Network and Microsoft.Compute among resource providers required for a fully provisionable subscription. However, those names are not offered as valid alternatives in this question. Microsoft.VirtualMachine is not the correct provider namespace—standard Azure compute uses Microsoft.Compute. Likewise, Oracle.Exadata is not the service namespace; Oracle AI Database@Azure resources are represented under Oracle.Database.

Therefore, among the supplied answer set, B and D are correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Azure subscription prerequisites, resource-provider registration and Oracle.Database integration.

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

Oracle AI Database@Azure does not eliminate the need for an OCI tenancy. Oracle explicitly requires an Oracle Cloud account/OCI tenancy during onboarding. A Public Offer creates a new tenancy, while a Private Offer can link an eligible existing tenancy or create one.

The other choices describe genuine architectural advantages. Oracle deploys its database infrastructure inside isolated areas of selected Microsoft Azure data centers, which places Oracle database resources physically close to Azure applications. This enables low-latency application-to-database communication through Azure networking rather than forcing production data traffic across the public internet to a distant OCI region.

Oracle also configures a managed connection between the Azure Child Site and geographically paired OCI Parent Site. The Parent Site hosts the Oracle control-plane components used to operate and manage the Oracle infrastructure located inside Azure.

The result is an architecture combining Azure-native application proximity and management integration with Oracle's database infrastructure and operational control.

Therefore, the claim that OCI tenancy requirements disappear is false, making A the correct "NOT a benefit" answer.

Study Guide reference: Introduction to Multicloud — Oracle AI Database@Azure architecture and multicloud benefits.

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

Oracle Exadata VM Cluster compute resources can be scaled down to zero OCPUs when the objective is to suspend compute consumption without deleting the VM Cluster definition or its persistent database storage. Oracle explicitly notes that simply stopping VMs does not stop the relevant compute billing; to stop VM Cluster compute-related billing, the enabled OCPU—or ECPU on applicable generations—allocation must be reduced to zero.

At zero enabled compute, the guest VMs are shut down while the infrastructure configuration and persistent database storage remain available. The administrator can later restore service by scaling the enabled compute allocation back above zero. This makes the feature useful for development, testing, seasonal, or otherwise intermittent environments where deleting and recreating the database environment would be operationally undesirable.

Values of one, two, or four OCPUs still represent allocated active compute and therefore do not achieve the requested zero-compute billing state.

On Exascale Infrastructure, Oracle documents the equivalent ECPU behavior explicitly: enabled ECPUs can be scaled to zero, shutting down VM Cluster VMs and stopping enabled-ECPU usage billing.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — VM Cluster scaling, OCPU/ECPU allocation and cost control.

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

Oracle documents a specific 404 NotAuthorizedOrNotFound condition that can occur during Exadata VM Cluster creation when the selected private DNS zone does not already contain tags. Oracle then attempts to generate the default OCI oracle-tags, but the multicloud service principal must have permission to use the associated tag namespace.

The required policy statement is:

Allow any user to use tag-namespaces in tenancy where request.principal.type = 'multicloudlink'

Oracle's current troubleshooting guidance also requires the companion permission:

Allow any user to manage tag-defaults in tenancy where request.principal.type = 'multicloudlink'

The crucial detail is that the provisioning operation executes under the multicloudlink principal type , not an ordinary administrator group or a principal with request.user.id='multicloud'. Merely granting inspect permission is insufficient because the service must actually apply the tag namespace/defaults.

Thus, among the supplied options, C is the required policy statement.

Study Guide reference: Secure Oracle AI Database@Azure — OCI IAM, MulticloudLink service principal and tagging permissions.

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

Oracle Autonomous Container Database backup configuration includes an explicit backup-retention policy on termination . Administrators can select one of two supported behaviors: retain backups according to the normal configured backup-retention period, or retain them for 72 hours after termination and then delete them .

Oracle documentation identifies these options as RETAIN_PER_RETENTION_WINDOW and RETAIN_FOR_72_HOURS. The latter is the default in relevant API/Terraform configuration. Therefore, terminating an Autonomous Container Database does not inherently result in the immediate deletion of all automatic backups. Their post-termination lifetime is governed by the configured termination-retention policy.

Standard automatic backups are also not automatically converted into Long-Term Retention backups when the database is terminated. LTR backups have their own lifecycle and are explicitly excluded from the ordinary ACD termination-retention setting. No automatic export to Azure Blob Storage occurs as part of ACD termination.

Thus, B correctly reflects Oracle's documented post-termination backup behavior.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Container Database automatic backups, termination and retention policy.

Oracle AI Database@Azure applies stricter hostname-prefix validation than the generic 63-character DNS-label maximum. For an Exadata VM Cluster, Oracle's DNS and network-design documentation specifies a maximum hostname-prefix length of 23 characters .

The value also has syntactic constraints. It must begin with a letter, end with an alphanumeric character, and can contain hyphens. Certain reserved values are prohibited. These restrictions exist because the supplied prefix becomes part of system-generated host and database-network names; Oracle must reserve additional character capacity for generated suffixes and service-specific naming constructs.

Therefore, 63 characters represents a general DNS-label ceiling but is not valid for this Exadata field. Thirty characters likewise exceeds the Oracle-specific limit, while 15 characters is unnecessarily restrictive.

The correct maximum is consequently 23 characters .

This is a configuration detail worth memorizing because hostname validation occurs during VM Cluster provisioning and an invalid prefix can block resource creation before the underlying Exadata compute nodes are deployed.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata VM Cluster DNS, hostname prefix rules and naming constraints.

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

A Hub-and-Spoke design separates shared connectivity and security services from workload networks. For Oracle AI Database@Azure, Oracle documents a Hub VNet that hosts centralized services such as Azure Firewall or a third-party NVA and a dedicated spoke VNet for Oracle AI Database@Azure containing the delegated subnet .

The Oracle database spoke is connected to the hub through Azure VNet peering. User-Defined Routes are then used to direct traffic through the hub's firewall or NVA when centralized inspection is required. Application spokes can similarly route database-bound traffic toward the security appliance, while return routes on the database spoke preserve the required symmetric traffic path.

Azure VM Scale Sets are application-compute constructs and do not form the essential Hub-and-Spoke network topology. OCI FastConnect is an OCI/hybrid connectivity capability rather than the Azure-side Hub-and-Spoke component described by this scenario.

Therefore, B and C identify the essential architecture: the Oracle database workload is isolated in a spoke VNet, while the Hub VNet provides centralized traffic inspection and security enforcement.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Hub-and-Spoke architecture, VNet peering, delegated subnet, Azure Firewall/NVA and UDR routing.

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

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.

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

The Network Anchor abstraction establishes the mapping between Azure networking resources and corresponding OCI networking constructs. It is particularly important for services that use the newer multicloud anchor model, allowing an Azure VNet and delegated subnet to be associated consistently with Oracle-managed resources.

Oracle's DNS documentation explicitly restricts the Network Anchor DNS-resolution capability in question to Oracle Base Database Service . Network Anchors can provide DNS integration between Azure and OCI, including inbound and outbound resolution paths. Depending on the configuration, DNS listening and forwarding functionality can be enabled so resources on either side of the multicloud boundary can resolve the required private names.

The question's "Replicate DNS Private zones during DB creation" behavior belongs to this Base Database Service Network Anchor DNS workflow. Exadata Database Service on Dedicated Infrastructure and Exadata Database Service on Exascale Infrastructure use their documented Exadata networking and DNS provisioning mechanisms. Autonomous AI Database likewise has its own networking lifecycle and is not the service to which this Network Anchor-specific private-zone replication setting applies.

Therefore, the database service required to expose the specified option is Oracle Base Database Service .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Network Anchors, private DNS, inbound/outbound DNS resolution, Base Database Service networking.

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

The delegated subnet is the Azure networking construct that enables Oracle-managed database resources to connect directly into the customer's Azure Virtual Network.

During Oracle AI Database@Azure provisioning, a subnet in the customer's VNet is delegated to the Oracle database resource provider. This delegation permits Oracle-managed networking components and database VNICs to participate in the Azure network while preserving the managed-service boundary between customer-owned Azure networking and Oracle-operated database infrastructure.

Applications can then connect privately and with low latency to the Oracle database through addresses associated with that delegated subnet. The customer can also apply supported Azure routing and security constructs around the VNet design.

A Local Peering Gateway connects OCI VCNs within an OCI region. A Dynamic Routing Gateway provides OCI routing between VCNs, on-premises environments, or remote networks. A Service Gateway provides private connectivity from an OCI VCN to supported Oracle services. None of these is the Azure-side resource that places Oracle database networking into the customer's VNet.

Thus, C. Delegated subnet is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet architecture and Azure VNet connectivity.

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

Oracle AI Database@Azure has specific client-subnet IP consumption requirements that must be considered during capacity planning. For the delegated client subnet, 13 IP addresses are reserved for networking services regardless of the number of VM Clusters deployed in that subnet .

Microsoft's Oracle AI Database@Azure networking documentation defines these 13 addresses as the first four addresses, the ninth through sixteenth addresses, and the final address of the subnet. Applied to 10.0.0.0/24, the reserved ranges are therefore 10.0.0.0–10.0.0.3, 10.0.0.8–10.0.0.15, and 10.0.0.255.

These platform reservations must be counted in addition to addresses needed for VM nodes and SCAN addresses. For example, every VM consumes multiple client-network addresses, and each VM Cluster requires SCAN addresses. Failing to account for the reserved block can therefore result in insufficient address capacity even when a subnet initially appears large enough.

Only option B precisely represents the documented reserved address positions.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet planning, client subnet sizing, reserved networking-service IP addresses and Exadata VM Cluster capacity.

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

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.

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

The uploaded study set keys D , because it attempts to preserve data inside the same geographical region while obtaining a separate fault domain.

There is, however, an important current-documentation qualification. Oracle AI Database@Azure maps an OCI Availability Domain to an Azure Availability Zone , and Oracle MAA documentation describes local Data Guard standby deployments on another Exadata infrastructure in the same or a separate Azure Availability Zone . Oracle's cross-zone Data Guard implementation explicitly requires primary and standby Oracle AI Database@Azure deployments in two supported Azure AZs.

Therefore, option D is valid only if the second OCI Availability Domain corresponds to another supported Oracle AI Database@Azure Azure AZ. If the premise is literally that Oracle AI Database@Azure is available in only one Azure AZ and cross-region replication is prohibited, current Oracle documentation does not provide a second independent Oracle AI Database@Azure site simply by selecting an unmapped OCI AD.

For the uploaded question's intended key, the answer remains D , but the architecture should be treated with this deployment-availability condition.

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

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.

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

Oracle Zero Downtime Migration is Oracle Maximum Availability Architecture's recommended orchestration framework for moving Oracle databases while minimizing production interruption. For physical online migration , ZDM uses Oracle Data Guard. The target database is instantiated as a physical standby, redo generated on the source is transported and applied to the target, and ZDM coordinates the eventual switchover. Oracle documentation for Oracle Database@Azure specifically states that physical online migration uses direct data transfer, Restore From Service, and Oracle Data Guard to keep source and target synchronized.

For logical online migration , the underlying synchronization technology is Oracle GoldenGate. Oracle Data Pump provides the initial logical export/import, after which GoldenGate captures ongoing source transactions and applies them to the target until cutover. This workflow can also accommodate scenarios involving different database versions or platforms.

Oracle Sharding is an application/data-distribution architecture rather than ZDM's replication mechanism. Far Sync is a Data Guard component for specialized zero-data-loss configurations but is not the primary technology identified for ZDM migration orchestration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM physical online migration, logical online migration, Data Guard, GoldenGate, Data Pump.

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

The appropriate architecture is Microsoft Entra ID-to-OCI SAML federation combined with group synchronization/mapping .

SAML provides the authentication component. Administrators authenticate using corporate Microsoft Entra ID identities and obtain federated access to the associated OCI Identity Domain. Oracle's onboarding procedure creates the SAML trust by exchanging metadata between Microsoft Entra ID and OCI.

The provisioning side then maps assigned users and groups from the Microsoft Entra enterprise application into OCI through the configured identity integration. This allows corporate group membership to drive the user's Oracle-side authorization model instead of requiring administrators to create and maintain separate OCI identities individually.

Azure RBAC governs Azure resources but does not by itself create the required OCI IAM group relationships for OCI Console administration. Azure Key Vault controls cryptographic keys and secrets rather than identity federation, while manually creating OCI users directly contradicts the automated identity-lifecycle requirement.

Therefore, A provides both SSO and centralized enterprise identity/group management.

Study Guide reference: Secure Oracle AI Database@Azure — SAML federation, user/group synchronization and OCI IAM.

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

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.

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

An Oracle AI Database@Azure delegated subnet remains part of the customer's Azure VNet and can use supported Azure networking controls. Two fundamental controls are Network Security Groups (NSGs) and Azure route tables containing User-Defined Routes .

An NSG performs traffic filtering by applying inbound and outbound security rules based on criteria such as source, destination, protocol, and port. This allows organizations to enforce database-access policies at the Azure network layer. Route tables provide forwarding control, allowing traffic to be directed through Azure Firewall, an NVA, a virtual network gateway, or other supported next-hop architecture.

Oracle's delegated-subnet design documentation explicitly states that because the delegated subnet belongs to the customer's VNet, it can leverage Azure networking capabilities including NSGs and routing tables . This enables private application-to-database communication while retaining enterprise routing and security controls.

Azure Load Balancer backend pools and Application Gateway ingress controllers are application/load-balancing constructs and are not the two subnet-associated controls identified for this Oracle database networking requirement.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet design, NSGs, Azure route tables, UDRs and traffic controls.

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

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.

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

Cross-availability-zone Oracle AI Database@Azure disaster recovery requires separate networking constructs for the primary and standby deployments. Oracle's Data Guard prerequisite documentation specifies two Azure VNets , with each VNet containing one Oracle AI Database@Azure delegated subnet , when configuring Data Guard between different availability zones in the same Azure region.

A separate delegated subnet ensures that each Exadata deployment receives the correct network attachment, address space, routing, and zone-aligned connectivity. Oracle also requires the associated VNet address spaces to be non-overlapping.

Reusing the AZ1 delegated subnet for infrastructure located in AZ2 would therefore conflict with the supported topology. Self-peering a subnet is not an Azure networking construct and would provide no meaningful isolation. Removing delegation would be counterproductive because delegation to Oracle's database resource provider is fundamental to provisioning Oracle AI Database@Azure networking.

Thus, A is the correct deployment pattern.

Study Guide reference: Configure Oracle AI Database@Azure Networking — cross-zone Data Guard networking, delegated subnets and VNet separation.

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

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.

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