Pass the Oracle Oracle Cloud Infrastructure 1z0-1147 Questions and answers with CertsForce

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.

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

Elastic resource allocation is a fundamental design characteristic of Oracle Exadata Database Service on Exascale Infrastructure . A VM requires a minimum of 8 enabled ECPUs at initial provisioning, but its compute allocation can subsequently be increased in 4-ECPU increments .

Oracle's Exascale architecture draws compute resources from Oracle-managed shared infrastructure rather than requiring the customer to purchase or provision dedicated database servers. This permits a customer to start with a relatively small footprint and increase capacity as workload requirements develop.

The workload therefore does not need to be migrated to Dedicated Infrastructure merely because additional processing power is required. Nor is it necessary to destroy and rebuild the VM Cluster or create an entirely new Exadata Infrastructure resource. Exascale is specifically intended to avoid those fixed-capacity operational patterns.

Oracle additionally supports online scaling of Exascale storage independently through the associated Database Storage Vault, reinforcing the service's elastic consumption model.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exascale elastic ECPU scaling.

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

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 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.

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

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 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.

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

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.

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

Purchasing and subscribing to the Oracle AI Database@Azure Private Offer establishes the Azure Marketplace commercial relationship, but it does not complete the technical onboarding process. The next mandatory stage is linking the Azure subscription to an Oracle Cloud Infrastructure tenancy . Oracle refers to this process as multicloud linking.

For a Private Offer, the customer can either create a new OCI tenancy or link an existing eligible OCI tenancy. The linked OCI account supplies the Oracle-side control-plane context used for database resources, including management of container databases and pluggable databases and delivery of Oracle infrastructure and software maintenance services. Only after the Purchase and Link stages have been completed and the account relationship is verified can normal Oracle AI Database@Azure resource provisioning proceed.

Azure Key Vault integration is optional and relates to customer-managed TDE keys. Data Guard is configured after database infrastructure exists, and an Autonomous Database is not a prerequisite for Exadata.

Therefore, D is correct. Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Purchase, Link, Verify, and OCI tenancy association.

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

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.

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

With the Default DNS option, Oracle automatically creates and manages the private DNS configuration associated with the Exadata VM Cluster. The generated database networking domain uses the oraclevcn.com suffix.

The Single Client Access Name (SCAN) listener and database-node FQDNs are registered within this Oracle-managed private DNS domain. OCI hosts the corresponding private DNS zone and, as part of the Oracle AI Database@Azure integration, the service replicates the required DNS records into a matching Azure Private DNS zone. Azure then links that private zone to the VNet hosting the Oracle database deployment, allowing Azure applications to resolve the Oracle database endpoints privately.

oraclecloud.com is broadly used for Oracle public cloud endpoints but is not the default private VCN suffix for the Exadata SCAN name. azure-database.net and oci-exadata.com are likewise not the default suffixes used by this Oracle-managed DNS architecture.

Therefore, D. oraclevcn.com is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata default DNS, SCAN and Azure Private DNS replication.

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