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

Oracle's current service-availability matrix states that Oracle Exadata Database Service on Dedicated Infrastructure is eligible for Private Offer only . It is not available through the Public Offer/Pay As You Go purchasing model.

Therefore, if an organization originally onboarded Oracle AI Database@Azure using the Public Offer and subsequently requires Dedicated Exadata Infrastructure, the commercial relationship must be changed by engaging Oracle Sales and obtaining the appropriate Private Offer .

A delegated-subnet service-limit increase affects networking capacity and does not enable a database service that is excluded by the selected Marketplace offer. BYOL can reduce Oracle Database licensing charges where eligible, but licensing model and Marketplace service eligibility are separate issues. Changing an Autonomous Database workload type is completely unrelated to Exadata hardware procurement.

Oracle's current service table also shows why the confusion can arise: Exadata Database Service on Exascale Infrastructure is available through both Public and Private Offers, whereas Exadata Database Service on Dedicated Infrastructure remains Private Offer only.

Therefore, A is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — offer eligibility and Dedicated Infrastructure purchasing.

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

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.

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

Oracle Active Data Guard Far Sync is specifically designed to provide zero-data-loss protection when the physical standby database is too geographically distant for direct synchronous redo transport without unacceptable primary-database latency.

The primary database sends redo synchronously to a nearby Far Sync instance. Because the Far Sync instance is positioned within low network latency of the primary, the primary can obtain the acknowledgement required for zero-data-loss protection without waiting for communication with the distant standby. Far Sync then forwards the redo asynchronously across the higher-latency interregional connection to the remote standby.

Oracle's Oracle Database@Azure reference architecture explicitly uses this pattern: the primary sends redo in SYNC mode to its local Far Sync instance, which forwards it in ASYNC mode to the remote standby database.

Maximum Performance using ASYNC alone permits a potential data-loss window. A snapshot standby is intended primarily for temporary read/write testing. Fast-Start Failover automates role transitions but requires an Observer and does not independently solve the synchronous-transport latency problem.

Therefore, C is correct. Study Guide reference: HA and DR — Active Data Guard Far Sync and zero-data-loss cross-region protection.

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

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.

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

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.

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

The foundational Exadata configuration is constructed from two distinct server tiers: database servers that execute Oracle Database workloads and Exadata Storage Servers that provide intelligent, scale-out database storage. Oracle's Exadata technical architecture identifies the base configuration as two database servers and three storage servers .

Two database servers provide the minimum database compute topology necessary for the architecture's availability and clustered database capabilities. A single database server would eliminate the server-level redundancy expected from the standard Exadata infrastructure design. On the storage side, three Exadata Storage Servers form the baseline storage configuration and support the redundancy mechanisms used by Oracle Automatic Storage Management and Exadata storage services.

Oracle documents the same two-database-server/three-storage-server starting configuration across current Exadata architectural material. Additional database or storage servers can be added in supported elastic configurations, but those expansions do not alter the minimum starting configuration asked for in the question.

Therefore, B and D are correct. Two storage servers are below the supported storage-server baseline, while one database server does not constitute the standard Exadata base infrastructure.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata Infrastructure architecture, database servers, storage servers, infrastructure sizing.

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

The invalid managed backup destination is the physical Zero Data Loss Recovery Appliance (ZDLRA) .

Oracle AI Database@Azure currently provides two primary managed automatic backup destinations for Exadata databases: Oracle Database Autonomous Recovery Service and OCI Object Storage . Oracle recommends Autonomous Recovery Service because it provides database-aware incremental-forever protection, policy-based retention, recoverability validation, optional real-time redo protection, and retention-lock capabilities.

Long-Term Retention is a supported capability of Recovery Service and allows selected backups to be preserved for extended compliance periods. It therefore represents a valid managed backup lifecycle option, even though technically it is a Recovery Service feature rather than an independent storage system.

The Zero Data Loss Recovery Appliance is a physical Oracle engineered system primarily used in customer data centers and appropriate Cloud@Customer architectures. Autonomous Recovery Service incorporates technologies derived from the Recovery Appliance but is delivered as a managed cloud service; these two should not be confused.

Therefore, the answer to the "NOT valid" question is B .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata automatic backups, Object Storage and Autonomous Recovery Service.

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

A Hub-and-Spoke design separates shared connectivity and security services from workload networks. For Oracle AI Database@Azure, Oracle documents a Hub VNet that hosts centralized services such as Azure Firewall or a third-party NVA and a dedicated spoke VNet for Oracle AI Database@Azure containing the delegated subnet .

The Oracle database spoke is connected to the hub through Azure VNet peering. User-Defined Routes are then used to direct traffic through the hub's firewall or NVA when centralized inspection is required. Application spokes can similarly route database-bound traffic toward the security appliance, while return routes on the database spoke preserve the required symmetric traffic path.

Azure VM Scale Sets are application-compute constructs and do not form the essential Hub-and-Spoke network topology. OCI FastConnect is an OCI/hybrid connectivity capability rather than the Azure-side Hub-and-Spoke component described by this scenario.

Therefore, B and C identify the essential architecture: the Oracle database workload is isolated in a spoke VNet, while the Hub VNet provides centralized traffic inspection and security enforcement.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Hub-and-Spoke architecture, VNet peering, delegated subnet, Azure Firewall/NVA and UDR routing.

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

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.

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

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.

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