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

Oracle Exadata VM Cluster compute resources can be scaled down to zero OCPUs when the objective is to suspend compute consumption without deleting the VM Cluster definition or its persistent database storage. Oracle explicitly notes that simply stopping VMs does not stop the relevant compute billing; to stop VM Cluster compute-related billing, the enabled OCPU—or ECPU on applicable generations—allocation must be reduced to zero.

At zero enabled compute, the guest VMs are shut down while the infrastructure configuration and persistent database storage remain available. The administrator can later restore service by scaling the enabled compute allocation back above zero. This makes the feature useful for development, testing, seasonal, or otherwise intermittent environments where deleting and recreating the database environment would be operationally undesirable.

Values of one, two, or four OCPUs still represent allocated active compute and therefore do not achieve the requested zero-compute billing state.

On Exascale Infrastructure, Oracle documents the equivalent ECPU behavior explicitly: enabled ECPUs can be scaled to zero, shutting down VM Cluster VMs and stopping enabled-ECPU usage billing.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — VM Cluster scaling, OCPU/ECPU allocation and cost control.

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

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.

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

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.

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

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.

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

During Exadata VM Cluster provisioning, the administrator selects the client delegated subnet and can explicitly provide a CIDR range for the Exadata backup network. If no backup-subnet CIDR is supplied, Oracle automatically uses the documented default of 192.168.252.0/22 .

The backup subnet serves Oracle database backup-network requirements and is architecturally distinct from the Azure delegated client subnet. Oracle's deployment-planning guidance emphasizes that the default backup CIDR is not part of the Azure VNet CIDR allocation. Nevertheless, address planning remains important. In disaster-recovery designs involving multiple Exadata deployments—especially cross-availability-zone or cross-region configurations—the administrator should explicitly choose non-overlapping backup CIDR blocks so that replication, routing, and backup traffic do not encounter conflicting address ranges.

Option B uses the correct network prefix but an incorrect /24 mask. Options A and D use different base networks and therefore do not match the Oracle provisioning default.

Accordingly, the correct response is C: 192.168.252.0/22 .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata VM Cluster client and backup networks, CIDR planning, default backup-subnet configuration and non-overlapping network design.

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

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.

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

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.

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

ZDM Physical Offline migration can use an Azure Files NFS share as the common location for RMAN backup files. Because the NFS share is mounted on both the source and target database hosts, file ownership must be interpreted consistently on both systems.

NFS using Unix-style permissions identifies users primarily by their numeric UID rather than simply by the textual account name. Oracle's ZDM migration guidance explicitly states that the NFS-mounted path is readable by the target database user only when the source database user's UID matches the target database user's UID. Thus, two hosts can both have an account named oracle, but if those accounts have different numeric UIDs, files created by one host can appear to be owned by a different identity on the other.

Port 443 and SQL*Net listener port 1521 address network/API or database-client connectivity; neither resolves Unix file ownership on an NFS mount. Active Directory Domain Services authentication is likewise not the controlling permission model for the documented NFS migration workflow.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Physical Offline migration, Azure Files NFS, RMAN backup staging and Linux UID permissions.

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

The Network Anchor abstraction establishes the mapping between Azure networking resources and corresponding OCI networking constructs. It is particularly important for services that use the newer multicloud anchor model, allowing an Azure VNet and delegated subnet to be associated consistently with Oracle-managed resources.

Oracle's DNS documentation explicitly restricts the Network Anchor DNS-resolution capability in question to Oracle Base Database Service . Network Anchors can provide DNS integration between Azure and OCI, including inbound and outbound resolution paths. Depending on the configuration, DNS listening and forwarding functionality can be enabled so resources on either side of the multicloud boundary can resolve the required private names.

The question's "Replicate DNS Private zones during DB creation" behavior belongs to this Base Database Service Network Anchor DNS workflow. Exadata Database Service on Dedicated Infrastructure and Exadata Database Service on Exascale Infrastructure use their documented Exadata networking and DNS provisioning mechanisms. Autonomous AI Database likewise has its own networking lifecycle and is not the service to which this Network Anchor-specific private-zone replication setting applies.

Therefore, the database service required to expose the specified option is Oracle Base Database Service .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Network Anchors, private DNS, inbound/outbound DNS resolution, Base Database Service networking.

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

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.

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