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

Oracle AI Database@Azure exposes database and infrastructure metrics through Azure Monitor, but similarly named metrics correspond to different levels of the Oracle resource hierarchy. Correct interpretation of the label is therefore essential.

Oracle's monitoring documentation explicitly differentiates the namespaces. OCI Database Cluster represents VM-cluster-level measurements. OCI Database represents Container Database (CDB) metrics. Oracle OCI Database identifies Pluggable Database-level metrics. Consequently, to examine CPU utilization for an individual PDB, the administrator selects CPU Utilization (Oracle OCI Database) .

This distinction is particularly important for consolidated Exadata environments. A cluster-level CPU metric can show overall infrastructure utilization but cannot determine which PDB is responsible for a workload spike. Similarly, CDB-level utilization aggregates activity at the container-database layer. The Oracle OCI Database-labelled metric enables the administrator to work at the PDB scope needed for tenant or application-specific performance analysis.

The Azure Monitor integration therefore provides several metrics with superficially similar names, but their resource dimensions are deliberately different.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Azure Monitor integration, Exadata monitoring, VM Cluster/CDB/PDB metric scopes and operational observability.

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

Oracle Base Database Service in Oracle AI Database@Azure is designed as a cost-effective single-instance database service , not as an Oracle RAC platform. Consequently, an architect selecting Base Database Service must recognize that multi-node Oracle Real Application Clusters are not available in this service configuration.

Oracle's current Oracle AI Database@Azure service comparison explicitly describes Base Database Service as shared infrastructure for running single instance Oracle Databases using general-purpose VM compute and network-attached storage. Where RAC-level database clustering is required, an Exadata-based service should be evaluated instead, because Oracle Exadata Database Service provides the clustered database architecture required for RAC.

The limitation is not associated with whether the older OCPU or newer ECPU compute model is used. Nor can a Base Database Service DB System become RAC merely by associating it with dedicated Exadata hardware; doing so would represent a different Oracle database service.

Therefore, the correct architectural constraint is C .

Study Guide reference: HA and DR with Oracle AI Database@Azure — Base Database Service availability architecture and RAC support.

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

Oracle Maximum Availability Architecture Silver adds Oracle Real Application Clusters (RAC) to the MAA Bronze foundation. RAC provides active-active database clustering across multiple database-server nodes while all instances access the same underlying database storage.

For Exadata Database Service on Dedicated Infrastructure, RAC supplies localized protection against database-instance and database-server failure. If one RAC instance or compute node fails, services and connections can relocate to surviving instances that are already running. RAC also materially reduces or eliminates database downtime for many planned maintenance operations.

Oracle Active Data Guard addresses a different availability layer: it maintains a physically separate standby database and is primarily used for site, availability-zone, or regional disaster recovery. Oracle GoldenGate performs logical data replication and integration, while Oracle Sharding distributes data across independent database shards for scale and fault isolation.

Oracle's current MAA documentation explicitly identifies RAC as the technology introduced at the Silver tier and recommends Exadata as the optimized RAC platform.

Therefore, B is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — MAA Silver, Oracle RAC and local high availability.

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

Oracle's current Oracle AI Database@Azure service matrix explicitly identifies Oracle Exadata Database Service on Exascale Infrastructure as eligible for both Private Offer and Public Offer purchasing models.

A Public Offer uses a pay-as-you-go Azure Marketplace model and allows customers to begin consuming supported services without first negotiating a custom contract with Oracle Sales. A Private Offer is based on negotiated commercial terms and is appropriate for enterprise commitments and customized pricing.

Exadata Database Service on Dedicated Infrastructure is Private Offer eligible but not Public Offer eligible. The same Private-Offer-only restriction applies to Autonomous AI Database on Dedicated Exadata Infrastructure. Oracle Database Autonomous Recovery Service is a database protection service rather than the alternative primary high-performance Exadata database platform requested by the scenario, and it is also listed as Private Offer only.

Exascale therefore combines Exadata database capabilities with a lower-entry, elastic shared-infrastructure model and marketplace flexibility.

Thus, A is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Azure Marketplace offers and available database services.

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

The -eval option invokes the evaluation workflow of Oracle Zero Downtime Migration rather than executing the production migration. Oracle specifically directs administrators to use ZDMCLI migrate database ... -eval to evaluate the migration process, including prerequisite checks, source/target connectivity verification, configuration validation, and applicable pre-migration assessment phases.

The resulting job is an evaluation job rather than a migration job that performs database movement. This distinction is reflected throughout ZDM command handling: ZDM can query evaluation jobs separately from actual migration jobs, and the evaluation workflow is intended to identify prerequisite or configuration failures before production data movement begins.

The option does not create a mock standby or execute a simulated Data Guard switchover. It also does not begin an offline migration and stop before the copy phase. CPAT may participate in migration-readiness assessment depending on ZDM version and command options, but -eval is not an installation command for CPAT.

Consequently, A correctly represents the effect: an EVAL-type workflow performs migration prechecks and validation without executing the actual migration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM CLI, evaluation mode, migration validation and prechecks.

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

Oracle's cross-region Oracle Database@Azure reference architecture requires an additional Hub VCN because each OCI VCN can be attached to only one Dynamic Routing Gateway (DRG) at a time.

The Oracle-managed database VCN associated with an Exadata VM Cluster already uses a DRG as part of the Oracle Database@Azure network architecture. Cross-region VCN peering also requires DRG-based remote peering. Because a second DRG cannot simply be attached to the existing database VCN, Oracle introduces a separate Hub VCN with its own DRG. The database VCN is locally connected to the Hub VCN, and the Hub DRGs establish the cross-region remote peering connection.

OCI documentation independently confirms that one VCN can attach to only one DRG, whereas a single DRG can support many VCN attachments. A VCN can also have multiple Local Peering Gateways, so option B is technically incorrect.

The limitation is therefore architectural rather than a restriction caused by Azure subnet delegation or tenancy boundaries.

Study Guide reference: HA and DR — OCI transit networking, Hub VCN, DRG, LPG and cross-region Data Guard.

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

A Network Anchor provides the cross-cloud network integration context used by supported Oracle AI Database@Azure services, including important DNS-resolution capabilities between Azure and OCI .

For inbound DNS resolution toward Azure, Oracle's Network Control Plane can create an OCI forwarding DNS endpoint and associated forwarding rules. For Azure-to-OCI resolution, the service can create an OCI listening DNS endpoint and expose its address through the Network Anchor so Azure DNS infrastructure or on-premises DNS servers can forward queries for Oracle database namespaces.

When both directions are configured, the architecture provides bidirectional private DNS resolution between Azure and OCI environments. Network Anchors can also participate in private-zone synchronization depending on the database service and DNS configuration.

The Network Anchor is not a cryptographic key store; TDE keys belong in Oracle Wallet, OCI Vault, Oracle Key Vault, or Azure Key Vault. Nor does the Network Anchor create Azure Availability Zones/OCI Availability Domains or mandate an IPsec-only intercloud transport mechanism.

Therefore, B is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Network Anchors, DNS listening endpoints and forwarding endpoints.

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.

Oracle AI Database@Azure applies a regional service limit to delegated subnet usage. The documented default is five delegated subnets per OCI tenancy in a specific region . This is a service quota rather than a limitation that can be bypassed through additional Azure routing constructs.

To exceed the default, the customer must request a service limit increase . Oracle identifies the relevant OCI service as Multicloud, the resource as Delegated Subnet Multicloud Links , and the corresponding service-limit name as azure-delegated-subnet-count. The limit is regional, so introducing another VNet, Route Server, VNet peering relationship, or Microsoft Entra tenant does not increase the permitted count.

Current documentation phrases the operation as requesting a service limit increase through Oracle's service-limit process. Among the supplied choices, option D is the only one that represents that required Oracle-side quota increase.

Architecturally, this distinction matters because routing topology and service capacity are independent control planes: networking objects determine reachability, whereas Oracle-enforced service limits determine how many delegated-subnet links may exist.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet limits and Multicloud service-limit management.

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

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.

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