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

Oracle Exadata Database Service on Exascale Infrastructure uses the Elastic Compute Processing Unit (ECPU) resource model. During initial VM Cluster provisioning, Oracle requires a minimum of 8 ECPUs enabled per VM .

The distinction between the initial minimum and subsequent scaling increments is important. After the VM Cluster exists, enabled compute capacity is adjusted in increments of 4 ECPUs . Therefore, 4 ECPUs represents the scaling granularity, not the minimum provisionable starting configuration. Oracle also allows enabled ECPUs to be reduced to zero after provisioning when administrators need to temporarily shut down the VMs and suspend enabled-ECPU usage billing, but zero cannot be used as the initial active configuration.

Current Oracle documentation defines the supported total ECPU allocation per VM within the applicable Exascale service limits and explicitly states that the provisioned value must be a multiple of four.

Consequently, neither 1 nor 4 meets the initial provisioning baseline, while 16 is valid but exceeds the minimum. The correct answer is A. 8 ECPUs .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exascale VM Cluster sizing and ECPU configuration.

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

The standard Oracle listener and SQL Net port used in the documented ZDM Physical Online migration workflow is TCP 1521 . Oracle's Oracle AI Database@Azure ZDM migration procedure explicitly instructs administrators to test SQL Net connectivity by running tnsping between source and target database hosts using port 1521.

This connectivity is required because ZDM and its underlying migration technologies must establish database-level communication for prechecks, configuration, target instantiation, Data Guard configuration, synchronization, and migration orchestration. If the source or target listener has been intentionally configured to use a nondefault port, that configured listener port must be permitted instead.

Port 22 is used for SSH administration between the ZDM Service Host and managed hosts. Port 443 is associated with HTTPS-based cloud service and API communication. Port 2049 is conventionally associated with NFS and is relevant when migration workflows use NFS-based staging, but it is not SQL*Net.

Therefore, D. 1521 is the correct answer.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM network prerequisites, SQL*Net and physical online migration.

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

The scenario directly matches Oracle's documented multicloud use case of running applications in one cloud and databases in another , also described here as an application and database split-stack architecture .

This design allows an organization to place its application tier in the cloud offering the preferred application-development ecosystem while retaining the database on the cloud platform offering the required database capabilities. In this case, Azure provides containerization and application modernization services, while OCI continues hosting Oracle Exadata Database Service for high transaction throughput, database availability, and Oracle-native operational control.

Private, high-bandwidth intercloud connectivity is critical because application-to-database latency directly affects transaction response time. Keeping data movement predictable and minimizing unnecessary public-internet routing also improves security and can reduce data-transfer overhead.

Horizontal workload distribution instead spreads workloads across clouds rather than separating application and database tiers. Production/development separation addresses lifecycle environments, while SaaS/ERP integration addresses data interoperability rather than a transactional split-stack application.

Therefore, C is the correct architectural pattern.

Study Guide reference: Introduction to Multicloud — Running Applications in One Cloud and Databases in Another.

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

Cross-availability-zone Oracle AI Database@Azure disaster recovery requires separate networking constructs for the primary and standby deployments. Oracle's Data Guard prerequisite documentation specifies two Azure VNets , with each VNet containing one Oracle AI Database@Azure delegated subnet , when configuring Data Guard between different availability zones in the same Azure region.

A separate delegated subnet ensures that each Exadata deployment receives the correct network attachment, address space, routing, and zone-aligned connectivity. Oracle also requires the associated VNet address spaces to be non-overlapping.

Reusing the AZ1 delegated subnet for infrastructure located in AZ2 would therefore conflict with the supported topology. Self-peering a subnet is not an Azure networking construct and would provide no meaningful isolation. Removing delegation would be counterproductive because delegation to Oracle's database resource provider is fundamental to provisioning Oracle AI Database@Azure networking.

Thus, A is the correct deployment pattern.

Study Guide reference: Configure Oracle AI Database@Azure Networking — cross-zone Data Guard networking, delegated subnets and VNet separation.

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

Oracle Application Continuity (AC) is the application-availability technology designed to mask recoverable database outages and replay database requests transparently after a connection is re-established.

Oracle RAC provides database-service continuity when one database instance or node becomes unavailable, but an application may still have active sessions or in-flight work on the failed instance. Application Continuity works with Oracle's high-availability connection infrastructure, database services, FAN, Transaction Guard, and supported clients to reconnect to an available instance and replay eligible database requests. This significantly reduces the application errors that would otherwise be exposed during node failure or planned maintenance.

Fast-Start Failover and Data Guard Broker operate at the Data Guard database-role and disaster-recovery level. They manage primary/standby transitions rather than transparently replaying an individual application session after a RAC node failure. Transparent Data Encryption protects database data at rest and has no role in request replay or failure masking.

Therefore, C. Oracle Application Continuity is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — RAC application availability, FAN, Transaction Guard and Application Continuity.

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

The Data Guard Observer is an independent process used by Fast-Start Failover to monitor the primary and standby databases and determine whether an automatic failover should occur. Because its independence directly affects the reliability of the failover decision, it should not share the same failure domain as either database.

For an Oracle AI Database@Azure architecture spanning availability zones, placing the Observer on a separate Azure VM in another availability zone provides appropriate fault isolation. If the primary AZ fails, the Observer remains available to verify the failure and initiate the transition to the standby. Hosting the Observer directly on the primary database node would cause it to disappear with a primary-site outage. Hosting it on the standby similarly creates an undesirable dependency on the standby environment.

The Observer is an external Data Guard Broker process; it does not belong inside Oracle's multicloud control-plane Parent Site. For stronger resilience, Oracle Data Guard can also support multiple observers in appropriate configurations.

Therefore, D represents the recommended architecture.

Study Guide reference: HA and DR with Oracle AI Database@Azure — Data Guard Broker, FSFO and Observer placement.

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

For an Autonomous AI Database Serverless target, Oracle Zero Downtime Migration supports Logical Online and Logical Offline migration workflows.

Logical migration is necessary because Autonomous AI Database Serverless abstracts the underlying physical database infrastructure and does not expose the file-system and database-host control required for a conventional physical RMAN/Data Guard migration. ZDM therefore operates through logical database migration technologies.

Logical Offline uses Oracle Data Pump export and import to instantiate the target. Logical Online adds Oracle GoldenGate to the workflow so changes occurring on the source after the initial data load are captured and applied to the target until final cutover, greatly reducing application downtime.

Oracle's Oracle Database@Azure migration documentation explicitly lists these two workflows for migration to Autonomous Database Serverless. Physical Online and Physical Offline workflows apply to supported customer-managed Oracle database targets, such as Exadata Database Service, rather than Autonomous Serverless.

Therefore, A is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — Autonomous AI Database Serverless migration workflow support.

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

Microsoft's Oracle Exadata Database on Dedicated Infrastructure observability guidance explicitly defines a no-duplicate-destination rule for these resources: two diagnostic settings cannot send the same log categories to the same destination. Each diagnostic-setting configuration must therefore remain unique.

An Exadata resource can have multiple diagnostic settings—Microsoft documents a maximum of five per resource—but those settings are intended to provide different category/destination combinations. If an administrator attempts to create another setting with the same log categories targeting the same Log Analytics workspace, the duplicate configuration is rejected rather than automatically consolidated.

Microsoft Sentinel does not serve as a conflict-management mechanism for the diagnostic-settings configuration, and the platform does not resolve the collision by modifying Log Analytics retention. Retention is a separate workspace/data-management concern.

This rule prevents unintended duplicate ingestion and avoids unnecessary telemetry duplication and associated ingestion cost.

Therefore, A accurately describes the outcome.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata logging, Azure Monitor diagnostic settings, Log Analytics and observability constraints.

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

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.

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

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.

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