1z0-1147 Questions and Answers

Oracle's Hub-and-Spoke design guidance defines an important UDR rule for Oracle AI Database@Azure delegated subnets: the route prefix must be at least as specific as the delegated subnet CIDR . A /24 delegated subnet therefore cannot be reliably represented by a broader /16 route when the architecture requires the delegated subnet-specific path.

The less-specific route can fail to take precedence over more-specific system or service routes. This creates the possibility that traffic takes one route toward the database but returns through a different route. Such asymmetric routing is especially problematic with Azure Firewall or an NVA because stateful firewalls expect both directions of a connection to traverse the same inspection point. If the return packet follows a different path, the firewall can drop the session.

A UDR has no mechanism for duplicating VNICs, changing SQL*Net encryption, or resizing the underlying subnet. It simply influences Layer-3 forwarding.

Therefore, A accurately describes the documented routing consequence.

Study Guide reference: Configure Oracle AI Database@Azure Networking — UDR prefix specificity, delegated subnet routing, Hub-and-Spoke and asymmetric routing prevention.

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

Oracle AI Database@Azure Network Anchors support DNS integration between Azure-side applications and OCI-side database networking. The two endpoint constructs used by Oracle DNS are the DNS forwarding endpoint and DNS listening endpoint .

For inbound DNS resolution from OCI toward Azure, Oracle's Network Control Plane can create a forwarding DNS endpoint and configure forwarding rules so OCI-hosted resources can forward queries toward the Azure DNS environment. Conversely, outbound resolution from Azure toward Oracle resources relies on an OCI listening DNS endpoint. The listening endpoint receives DNS requests and enables Azure or connected on-premises systems to resolve Oracle AI Database@Azure names.

The terminology is important. Oracle explicitly uses listening and forwarding endpoint constructs. "DNS replication endpoint" is not the endpoint name used for private-zone synchronization, and "DNS peering endpoint" is not an Oracle Network Anchor endpoint type. DNS-record synchronization is a separate behavior from the endpoint resource itself.

Consequently, the correct selections are A and D .

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

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

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.

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

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's cross-region Oracle Database@Azure reference architecture requires an additional Hub VCN because each OCI VCN can be attached to only one Dynamic Routing Gateway (DRG) at a time.

The Oracle-managed database VCN associated with an Exadata VM Cluster already uses a DRG as part of the Oracle Database@Azure network architecture. Cross-region VCN peering also requires DRG-based remote peering. Because a second DRG cannot simply be attached to the existing database VCN, Oracle introduces a separate Hub VCN with its own DRG. The database VCN is locally connected to the Hub VCN, and the Hub DRGs establish the cross-region remote peering connection.

OCI documentation independently confirms that one VCN can attach to only one DRG, whereas a single DRG can support many VCN attachments. A VCN can also have multiple Local Peering Gateways, so option B is technically incorrect.

The limitation is therefore architectural rather than a restriction caused by Azure subnet delegation or tenancy boundaries.

Study Guide reference: HA and DR — OCI transit networking, Hub VCN, DRG, LPG and cross-region Data Guard.

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

The purchase process creates an Azure-managed resource group in the background to host the OracleSubscription resource used for Oracle AI Database@Azure billing and subscription integration. Microsoft specifically documents a known issue in which Azure Policy can block this operation.

The system-created managed resource group must initially be located in EastUS , must conform to the provider-defined naming requirement, and is initially created without tags . Consequently, an enterprise policy that allows only West Europe or denies untagged resource groups prevents the OracleSubscription resource from being created. The correct remediation is to exempt the applicable managed resource group from those blocking policies during the purchase process. Microsoft recommends identifying the blocking assignment in the Azure activity log and creating an appropriate, preferably time-bound, Azure Policy exemption.

Administrators cannot solve the problem by manually creating their own resource group in West Europe because this is a provider-managed resource. Billing-address changes likewise do not change the resource provider's required deployment location, and OCI commercial-model changes do not remove the Azure OracleSubscription requirement.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — private offer purchase, OracleSubscription resource, Azure prerequisites and policy considerations.

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

The appropriate built-in Azure RBAC role is Monitoring Contributor . Microsoft defines this role for administrators who need to read monitoring information and create or modify monitoring configuration .

Monitoring Contributor includes the monitoring-read capabilities required to inspect metrics and diagnostic data and adds permissions needed to create or edit diagnostic settings, alert-related configurations, and monitoring resources. Microsoft also identifies creation of private monitoring dashboards as a supported use case for this role.

Monitoring Reader is insufficient because it is primarily a read-only monitoring role. It allows users to inspect monitoring data and settings but does not grant the required configuration-modification permissions. The general Reader role similarly lacks write capabilities. Owner would technically provide sufficient access but violates least privilege because it grants comprehensive resource-management permissions, including access-control authority far beyond monitoring.

Because the administrator's duties are specifically monitoring-oriented but require configuration changes, Monitoring Contributor supplies the correct functional scope without granting unrestricted ownership.

Study Guide reference: Secure Oracle AI Database@Azure — Azure RBAC, monitoring permissions, least privilege and operational administration

Oracle AI Database@Azure has a default regional service limit of five delegated subnets . Once a deployment requires more than five delegated subnet links in a region, the customer must request a service-limit increase.

This aggregate regional limit must not be confused with the separate VNet design rule. An individual Azure VNet can contain a maximum of one delegated subnet for Oracle AI Database@Azure, but an organization can have several VNets and therefore several delegated subnets across the same region up to the default service limit.

Oracle identifies the relevant service-limit metadata as:

Service: Multicloud

Resource: Delegated Subnet Multicloud Links

Limit name: azure-delegated-subnet-count

The limit operates at regional scope. Therefore, creating additional peerings or Route Servers does not bypass it; the correct approach is to request additional service capacity through Oracle's service-limit process.

Values of 1, 3, and 10 do not represent the default regional limit.

Therefore, A. 5 is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet quotas and service-limit increases.

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

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.

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

Oracle's multicloud guidance identifies business and architecture patterns rather than narrowly defined infrastructure features as core multicloud use cases. Two explicitly documented patterns are Cross-Cloud Disaster Recovery and Running Applications in One Cloud and Databases in Another .

Cross-cloud disaster recovery places a production environment in one cloud while maintaining a recovery environment in another. This design reduces dependence on a single cloud platform and enables business continuity if the primary environment experiences a major outage. It is particularly relevant where resilience requirements justify provider-level diversification.

The application/database split pattern allows an organization to operate its application tier in one cloud while placing its database in another cloud that provides preferable database capabilities, performance, economics, or management characteristics. Oracle AI Database@Azure is a practical implementation of this model: Azure applications can use Oracle database technology deployed in Azure data centers and managed through Oracle's multicloud architecture.

Automatic identity-domain replication and Active Directory domain-controller synchronization may support a multicloud environment, but they are implementation capabilities rather than the high-level multicloud use cases documented by Oracle.

Study Guide reference: Introduction to Multicloud — multicloud drivers, application/database separation, cross-cloud DR, resiliency and workload placement.

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

For a cross-region Autonomous Data Guard standby , Oracle specifies a maximum possible data-loss objective of approximately 1 minute . Accordingly, the intended Recovery Point Objective is one minute.

Cross-region protection differs from a local Autonomous Data Guard standby because geographical distance makes fully synchronous zero-data-loss transport impractical for normal cross-region operation. Oracle therefore uses an asynchronous protection model that provides a bounded RPO while maintaining acceptable database performance.

A useful distinction is between RPO and RTO. RPO measures potential data loss, whereas RTO measures how long restoration of service is targeted to take. Oracle's current Autonomous AI Database Serverless SLO documentation continues to specify a 1-minute cross-region RPO . Current documentation has improved the cross-region RTO target to less than 10 minutes ; older material cited approximately 15 minutes. That RTO evolution does not affect the answer to this question because only RPO is being tested.

Zero data loss therefore applies to different protection scenarios, while five and fifteen minutes do not represent the documented cross-region RPO.

Study Guide reference: HA and DR — Autonomous Data Guard local and cross-region recovery objectives.

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

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.

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

Oracle Autonomous AI Database Serverless documents a local Autonomous Data Guard standby RTO SLO of two minutes for failure events that require failover to the standby.

For the Recovery Point Objective, current Oracle documentation is slightly more precise than the wording in option A: the local standby's maximum possible data-loss objective is less than 10 seconds . Therefore, the exam option stating "RPO of 10 seconds" represents the intended and closest supported value.

These SLOs apply to events such as full database failure, complete storage failure, corruption scenarios requiring standby transition, and availability-domain failures when Autonomous Data Guard is enabled. Local standby protection provides materially faster recovery and a substantially smaller possible data-loss window than cross-region standby protection because replication remains geographically close.

An hour-long RTO is inconsistent with active standby protection, while five-minute RPO and thirty-second RPO values do not match Oracle's stated local Autonomous Data Guard objectives.

Therefore, A is correct, interpreted technically as 2-minute RTO and <</b> 10-second RPO .

Study Guide reference: HA and DR — Autonomous Data Guard local standby SLOs.

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