Oracle Updated 1z0-1147 Exam Questions and Answers by alvey

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.

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

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.

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

Oracle Exadata Database Service on Exascale Infrastructure separates database storage into Exascale Database Storage Vaults . Oracle documents the minimum billed Database Storage Vault capacity as 300 GB per VM Cluster .

The minimum is composed of storage required for system use and the first database. Oracle's current Exascale capacity table allocates 50 GB for system-related usage, including images stored in ACFS, and 250 GB for database use when provisioning the first database. Together, these produce the 300 GB minimum vault capacity.

This value must not be confused with VM file-system storage. Current Exascale guidance specifies a separate minimum VM file-system capacity that varies by database version—for example, 220 GB for a 26ai VM configuration. That explains why 220 GB appears plausible but is incorrect for the Database Storage Vault asked about here.

The vault can subsequently be scaled substantially beyond the minimum; Oracle documents VM Cluster Exascale Vault storage scaling up to 100 TB.

Therefore, the correct answer is D. 300 GB .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata Database Service on Exascale Infrastructure, Database Storage Vault sizing and capacity.

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

Oracle Autonomous AI Database Serverless allows administrators to configure the automatic backup-retention window according to business recovery and compliance requirements. Oracle's current Autonomous AI Database provisioning documentation specifies an allowable automatic backup-retention range of 1 through 60 days .

Within that period, the database can be restored and recovered to an appropriate point in time, subject to the normal Autonomous AI Database backup and recovery mechanisms. A longer retention window provides a broader point-in-time recovery horizon but must also be considered alongside governance, compliance, and backup-protection requirements.

Oracle also supports Backup Retention Lock , which materially changes administrative behavior. When the retention period is locked, administrators cannot simply disable the lock or alter the protected retention setting through ordinary provisioning controls; Oracle Support intervention is required for those changes. This distinction is important for regulated workloads where backup immutability or protection from malicious administrative actions is required.

The alternatives beginning at seven days incorrectly raise the minimum, while the 30-day options incorrectly reduce the supported maximum. The complete configurable range is therefore 1–60 days .

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous AI Database automatic backups, point-in-time recovery, backup-retention configuration and retention lock.