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

Under the default managed-DNS model, Oracle derives the private Oracle domain from normalized VNet and delegated-subnet naming components. In the source scenario, the production and DR resource names share the same leading characters, causing both sites to derive the same oraclevcn.com private DNS namespace.

The practical resolution is therefore to alter the naming inputs before deployment so the generated DNS labels are unique. The uploaded question set specifies that the relevant generated tokens use the first 11 alphanumeric characters , so either the DR VNet or delegated subnet must be renamed such that the derived prefix differs from the active environment.

The Host Domain Name field associated with default managed DNS is system-generated rather than freely editable. Adding another DNS resolver does not eliminate the underlying duplicate private-zone namespace, and DNS views cannot reliably correct a collision created at resource provisioning.

Therefore, D resolves the root cause while retaining Oracle-managed DNS.

Study Guide reference: Configure Oracle AI Database@Azure Networking — default DNS, oraclevcn.com, VNet/subnet DNS derivation and DR naming design.

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

Oracle's current onboarding documentation explicitly states that customers purchasing through the Public Offer (Pay As You Go) must create a new OCI tenancy during onboarding.

The Public Offer is purchased directly in Azure Marketplace without negotiating a contract with Oracle Sales. Billing occurs through Azure, usage can count toward Microsoft Azure Consumption Commitment, and customers can start or stop consumption without a predetermined usage commitment. However, the trade-off relevant to this question is that an existing OCI tenancy cannot be linked to a Public Offer.

The Private Offer is different. Private Offer customers negotiate commercial terms with Oracle and can either link an eligible existing OCI tenancy or create a new OCI tenancy during onboarding.

Bring Your Own License affects Oracle Database software licensing economics rather than defining the Marketplace onboarding path. Universal Credits is likewise an OCI commercial construct and is not the Public/Private Oracle AI Database@Azure offer selection being tested.

Therefore, B is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Public Offer, Private Offer and OCI tenancy requirements.

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

The correct staging medium is an Azure Files NFS share . Oracle's ZDM documentation for Autonomous AI Database Serverless on Oracle Database@Azure explicitly supports Azure Files as an NFS file-share source for Data Pump migration staging.

In the logical migration workflow, the NFS share is made accessible to the source database and attached to the Autonomous AI Database target. Data Pump export files can therefore be written to and read from the shared location without being staged in OCI storage. Oracle specifically documents mounting Azure Files NFSv4.x and exposing the path through a database directory for Data Pump operations.

OCI Object Storage and OCI File Storage would place the staging data within OCI, violating the explicit requirement that dump files remain in the Microsoft Azure subscription. Azure Blob Storage can be accessed by Autonomous Database through DBMS_CLOUD for supported object-storage workflows, but the standard ZDM NFS-based Data Pump staging mechanism described in this question uses a mounted filesystem rather than a direct Blob REST API.

Therefore, C is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM, Autonomous AI Database Serverless, Data Pump and Azure Files NFS.

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

Logical Online Migration combines an initial logical data load with Oracle GoldenGate change data capture to minimize production downtime.

The initial target database is populated using Oracle Data Pump export and import. Because that data movement can take a substantial amount of time for large databases, Oracle GoldenGate continuously captures transactions committed on the source while the initial load is being performed. Those transactions are subsequently applied to the target, allowing the destination to converge with the production source while the application remains active.

When synchronization reaches the required state, ZDM orchestrates the final migration phases and application cutover. The downtime requirement is therefore concentrated around the final transition rather than the entire export/import window.

Logical Offline uses Data Pump without continuous GoldenGate synchronization. Physical Online uses RMAN-based target instantiation and Oracle Data Guard redo synchronization instead of GoldenGate. Physical Offline similarly relies on physical backup/restore processes and does not use logical change-data capture.

Thus, B. Logical Online Migration is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Logical Online, Data Pump and GoldenGate CDC.

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

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.

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

The standard Oracle Autonomous AI Database Serverless resource-allocation interface permits the administrator to configure the base compute allocation up to 512 ECPUs using the ECPU slider. This value represents the configured base ECPU count for a single database instance rather than the potential temporary compute consumption obtainable through compute auto scaling.

Oracle distinguishes configured ECPUs from auto-scaled usage. For eligible Autonomous AI Database configurations, compute auto scaling can allow the database to consume additional processing capacity above the configured base according to workload demand. For example, a database configured with 512 ECPUs may be capable of consuming substantially more effective processing capacity when auto scaling is enabled, subject to the service and licensing model.

The 1024-ECPU option therefore does not represent the normal single-instance slider ceiling addressed by this question. The 256- and 128-ECPU values are valid intermediate configurations but are below the maximum.

Consequently, A. 512 ECPUs is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database Serverless provisioning, ECPU configuration and compute scaling.

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

Oracle Database Autonomous Recovery Service supports Long-Term Retention (LTR) backups for organizations that need to preserve full database backups for compliance, regulatory, legal, or business requirements. The correct destination is the OCI Object Storage Infrequent Access tier .

The question source specifies that the LTR backup initially remains in the standard storage tier and transitions after the first 24 hours to Infrequent Access storage for the remainder of its retention period. Oracle's Recovery Service documentation independently confirms that long-term retention backups are stored in the Object Storage Infrequent Access tier and can be retained for periods extending up to ten years.

The Infrequent Access tier is appropriate because LTR backups are retained for extended periods but are generally restored less frequently than operational backups. Archive Storage is not the managed destination used by Recovery Service for this workflow. Azure Archive Blob Storage is likewise not the Oracle-managed OCI storage tier identified for these backups, and there is no "OCI Legacy Backup" storage tier.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous Recovery Service, LTR backups, retention and storage lifecycle.

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

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 Zero Downtime Migration organizes its Oracle database migration methods into two fundamental workflow families: Physical Migration and Logical Migration . Each family can then have online and offline variants depending on compatibility requirements and acceptable downtime.

Physical migrations operate on the physical database representation and rely on technologies such as RMAN and Oracle Data Guard. Physical Online migration can instantiate a target using Restore From Service and maintain synchronization using Data Guard, while Physical Offline uses RMAN backup and restore.

Logical migrations operate through logical database objects and data. Oracle Data Pump provides the initial export/import mechanism, while Logical Online migration integrates Oracle GoldenGate to capture and replicate ongoing transactions before cutover. Logical workflows are also suitable for many cross-version or cross-platform scenarios that physical workflows cannot support.

"Container-based migration" and "snapshot-based migration" are not ZDM's top-level migration workflow categories.

Oracle's current ZDM documentation explicitly states that ZDM supports both Physical and Logical Migration workflows.

Therefore, B and D are correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM workflow categories.

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

Oracle AI Database@Azure integrates its operational telemetry with Azure Monitor diagnostic settings so organizations can apply existing Azure observability, compliance, and SIEM architectures to Oracle database infrastructure.

Three standard destinations are relevant here. An Azure Log Analytics workspace receives telemetry for centralized querying, dashboarding, alerting, and Kusto Query Language analysis. An Azure Storage account can archive logs or metrics for retention, compliance, or later processing. Azure Event Hubs provides a streaming destination for forwarding telemetry to SIEM products, custom consumers, event-processing pipelines, or other downstream platforms.

Oracle's Oracle AI Database@Azure monitoring documentation specifically lists Log Analytics Workspace, Storage Account, and Event Hub among the available Azure Monitor diagnostic-routing destinations. Oracle Enterprise Manager can monitor Oracle environments but is not an Azure Monitor diagnostic-settings destination. OCI Object Storage is likewise not selected directly as a destination from the Azure diagnostic-settings workflow. Azure SQL Database is a database service rather than a supported diagnostic sink.

Therefore, the three correct selections are A, C, and D .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — monitoring, Azure diagnostic settings, Log Analytics, Storage accounts and Event Hubs.

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