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

ZDM manages migrations as persistent scheduled jobs and assigns each job a unique job ID. Administrators must manipulate these jobs through the supported ZDMCLI lifecycle commands rather than modifying ZDM repository or log files manually.

Oracle documents the command zdmcli abort job -jobid < job_id > for terminating a specified ZDM job. When an existing job context is preventing a new migration workflow from being established for the same source, the supported administrative approach among the available options is to identify the existing job and abort it through ZDMCLI.

Restarting the ZDM service does not remove the persistent job record; the job metadata is maintained by ZDM rather than existing only in the running daemon's memory. Manually deleting files from ZDM directories is unsupported and risks corrupting or desynchronizing job state. Likewise, the proposed -ignore ALL option is not a supported mechanism for bypassing ZDM's migration-job lifecycle controls.

Consequently, B is the correct operational command because it acts on the existing migration through the supported ZDM control interface.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDMCLI job management, query/abort operations and migration workflow lifecycle.

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

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's reference architecture for multi-region Oracle Database@Azure disaster recovery explicitly states that no subnet is required in the Hub VCN to enable transit routing .

The Hub VCN serves primarily as a routing construct connecting gateways and route-table attachments. DRGs, Local Peering Gateways, Remote Peering Connections, and VCN route tables provide the required network forwarding between the Oracle Database@Azure Child Site VCNs and remote regions. Because the hub does not need to host compute instances or network virtual appliances for this gateway-based transit model, it does not require a workload subnet.

This has an additional design benefit: the hub VCN can use a comparatively small CIDR range because there is no requirement to reserve substantial address space for servers or VNICs.

A public subnet and Internet Gateway are unnecessary because Data Guard traffic should traverse private cloud networking. Likewise, dedicated /24 transit-appliance subnets or per-availability-domain private subnets are not mandatory for the gateway-based topology.

Therefore, D is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — cross-region Data Guard, OCI Hub VCN and transit routing.

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

Oracle Exadata Database Service on Exascale Infrastructure is eligible for both the Private Offer and Public Offer , with the Public Offer representing the Pay As You Go marketplace model.

A Private Offer is negotiated with Oracle and can include custom pricing, contract terms, usage commitments, and enterprise commercial arrangements. After agreement, the customer accepts the private offer through Azure Marketplace.

A Public Offer allows supported Oracle AI Database@Azure services to be purchased directly from Azure Marketplace without first negotiating a private commercial agreement. Oracle describes this model as Pay As You Go, with no predetermined usage commitment. Oracle's current Azure service table explicitly lists Exadata Database Service on Exascale Infrastructure as eligible for both offer types.

Azure Reserved Instance pricing is an Azure compute purchasing construct and is not one of the Oracle AI Database@Azure offer mechanisms. Oracle also specifies that free-trial subscription models are not the purchasing path for these multicloud database resources.

Therefore, B and C are correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Public Offer, Private Offer and Exascale purchasing.

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

The intended topology is Hub-and-Spoke with centralized NVA inspection , making C the correct choice among the available answers. This architecture permits multiple application VNets to communicate privately with the Oracle database while routing inter-VNet traffic through a central firewall or Network Virtual Appliance rather than the public internet.

There is an architectural wording issue worth correcting precisely. Oracle's published reference topology normally places the Azure Firewall/NVA in the Hub VNet while Oracle Database@Azure resides in a separate Data VNet containing the delegated client subnet . Application workloads reside in spoke VNets. The hub then provides centralized routing and inspection between the application spokes and the data VNet.

Therefore, the essential principle embodied by C— Hub-and-Spoke plus centralized NVA inspection —is correct, although the phrase "delegated subnet in the hub VNet" is not how Oracle's canonical diagram lays out the components.

Direct local peering would bypass centralized inspection, while direct Virtual WAN spoke-to-spoke communication violates the same requirement. Data Guard concerns DR, not application traffic inspection.

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

The default encryption-key model for an Exadata database on Oracle AI Database@Azure is Oracle-Managed Keys (OMK) . Under this model, Oracle automatically generates the Transparent Data Encryption master encryption key and stores it in an Oracle Wallet secured within the database environment.

Oracle manages the complete lifecycle of this default key, including generation, secure storage, rotation, backup, and restoration. No additional customer-side key-management infrastructure is required.

OCI Vault, Oracle Key Vault, and Azure Key Vault represent customer-managed key alternatives. When an organization selects one of these mechanisms, the TDE master key is managed outside the local Oracle Wallet, enabling centralized customer control, auditing, rotation policy, and separation of duties. However, none is the default unless the customer explicitly configures a customer-managed key architecture.

Oracle's current security documentation explicitly identifies Oracle Wallet as the default encryption-key setting for Exadata Database Service on Oracle AI Database@Azure.

Therefore, C. Oracle Wallet is correct.

Study Guide reference: Secure Oracle AI Database@Azure — TDE, Oracle-managed keys and Oracle Wallet.

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

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.

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

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 migrations to Autonomous Database Shared/Serverless , ZDM applies automatic tablespace remapping because users cannot freely reproduce arbitrary source tablespaces in the same manner as on a customer-managed Oracle Database.

Oracle's ZDM documentation states that for an Autonomous Database Shared Infrastructure target, source tablespaces are automatically remapped to the predefined DATA tablespace by default. In FULL-mode migration to Autonomous Database Serverless, Oracle likewise specifies DATA as the default remap target because general user-created tablespace creation is not supported in that migration model.

This prevents source schema objects from being imported into unavailable tablespaces. SYSTEM and SYSAUX are Oracle-maintained dictionary tablespaces and must not be used as ordinary user-data destinations. USER_DATA is not the standard default target identified by ZDM. Preserving every source tablespace name is also incompatible with the default Autonomous Serverless storage model.

ZDM can support explicit metadata remapping where appropriate, but absent such an override, the default is DATA.

Therefore, D is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM logical migration, Data Pump and automatic tablespace remapping.

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

Oracle Active Data Guard Far Sync is specifically designed to provide zero-data-loss protection when the physical standby database is too geographically distant for direct synchronous redo transport without unacceptable primary-database latency.

The primary database sends redo synchronously to a nearby Far Sync instance. Because the Far Sync instance is positioned within low network latency of the primary, the primary can obtain the acknowledgement required for zero-data-loss protection without waiting for communication with the distant standby. Far Sync then forwards the redo asynchronously across the higher-latency interregional connection to the remote standby.

Oracle's Oracle Database@Azure reference architecture explicitly uses this pattern: the primary sends redo in SYNC mode to its local Far Sync instance, which forwards it in ASYNC mode to the remote standby database.

Maximum Performance using ASYNC alone permits a potential data-loss window. A snapshot standby is intended primarily for temporary read/write testing. Fast-Start Failover automates role transitions but requires an Observer and does not independently solve the synchronous-transport latency problem.

Therefore, C is correct. Study Guide reference: HA and DR — Active Data Guard Far Sync and zero-data-loss cross-region protection.

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