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

Oracle explicitly requires Advanced Networking for compatibility between Oracle AI Database@Azure and certain Azure services that use specialized private-networking behavior. Oracle's troubleshooting documentation specifically identifies Azure Container Apps and serverless services such as Azure Functions using private endpoints as examples.

Without Advanced Networking, these services may be unable to establish supported connectivity to the Oracle AI Database@Azure delegated subnet even when basic VNet routing appears correct. The feature enables the enhanced networking capabilities required for these communication patterns and is also relevant to Global VNet Peering scenarios.

Oracle notes an important provisioning condition: Advanced Networking should be enabled before Oracle AI Database@Azure resources/VNICs have been provisioned in the delegated subnet for the feature to be applied correctly to subsequent resources.

An NVA route bypass does not provide this compatibility feature. FastConnect is an OCI dedicated-connectivity technology, and ExpressRoute Global Reach addresses ExpressRoute interconnection scenarios rather than the specific Azure Container Apps compatibility requirement.

Thus, C. Advanced Networking is the documented solution.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Advanced Networking, delegated subnet connectivity, Azure Container Apps and serverless/private endpoint integration.

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

Oracle Exadata Database Service on Exascale Infrastructure uses the Elastic Compute Processing Unit (ECPU) model for allocating database-server processing capacity. Oracle's Exascale technical architecture specifies that a VM requires at least eight enabled ECPUs for initial VM Cluster provisioning and that vertical compute scaling is performed in increments of four ECPUs .

This model provides substantially finer-grained scaling than traditional fixed Exadata infrastructure shapes while maintaining predictable resource allocation across the underlying Exascale compute pool. Administrators can increase enabled ECPUs as workload demand grows, and Exascale also supports reserved ECPU concepts that allow capacity to be physically reserved for future growth. The distinction between enabled and reserved capacity is operationally important: enabled ECPUs are active compute resources used by the VM, whereas reserved capacity can facilitate future scale-up.

An increment of eight would unnecessarily double the required scaling step; one- or two-ECPU increments are not the documented unit for Exadata VM scaling on Exascale Infrastructure. The correct granularity is therefore four ECPUs .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exadata Database Service on Exascale Infrastructure, ECPU compute model, VM Cluster provisioning and scaling.

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

Oracle Database Autonomous Recovery Service with Azure-based storage is specifically designed to satisfy this combination of data residency, ransomware protection, near-zero data loss, and Azure commercial integration.

Oracle allows the protection policy to specify Store backups in the same cloud provider as the database , which keeps Oracle Database@Azure Recovery Service backups within Azure rather than the paired OCI region. A protection policy can also enable Retention Lock , preventing backups from being modified or deleted before policy expiration and providing protection against accidental or malicious deletion.

For business-critical databases, Real-time Data Protection can be enabled. Oracle describes this as providing recovery to the last sub-second, materially reducing potential data-loss exposure compared with ordinary periodic backups.

Oracle AI Database@Azure usage is billed through Azure Marketplace and counts toward Microsoft Azure Consumption Commitment. Standard OCI Object Storage would not satisfy the stated local-Azure-only storage requirement. Customer-managed Blob Storage lacks the integrated Recovery Service real-time protection model, while ZDLRA is an engineered on-premises recovery appliance rather than the native Oracle AI Database@Azure service.

Therefore, B is correct.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Recovery Service, retention lock, real-time protection and data residency.

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

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.

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

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.

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

Oracle's Oracle AI Database@Azure prerequisites explicitly identify the personas required for optional identity federation. On the Azure side, the required persona is an Entra ID Administrator with appropriate Microsoft Entra administrative permissions. On the OCI side, the corresponding persona is an Identity Domain Administrator .

This combination is necessary because federation spans both identity systems. Microsoft Entra ID must be configured with the OCI enterprise application, SAML authentication details, groups/users, and provisioning configuration. OCI IAM Identity Domains must then trust the Entra identity provider, establish the corresponding IdP configuration and policies, and support any required user provisioning.

Oracle's prerequisite matrix specifically lists Azure permissions including External Identity Provider Administrator, Groups Administrator, and User Administrator capabilities, with OCI Identity Domain Administrator permission on the Oracle side.

Billing Account Owner, Subscription Owner, Support Owner, and Security Zone Administrator roles serve different administrative purposes and do not jointly provide the identity-domain configuration authority required for federation.

Therefore, B exactly matches Oracle's documented administrative personas.

Study Guide reference: Secure Oracle AI Database@Azure — identity federation, Microsoft Entra ID, OCI IAM Identity Domains, SSO and RBAC.

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

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 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 appropriate built-in Azure RBAC role is Monitoring Contributor . Microsoft defines this role for administrators who need to read monitoring information and create or modify monitoring configuration .

Monitoring Contributor includes the monitoring-read capabilities required to inspect metrics and diagnostic data and adds permissions needed to create or edit diagnostic settings, alert-related configurations, and monitoring resources. Microsoft also identifies creation of private monitoring dashboards as a supported use case for this role.

Monitoring Reader is insufficient because it is primarily a read-only monitoring role. It allows users to inspect monitoring data and settings but does not grant the required configuration-modification permissions. The general Reader role similarly lacks write capabilities. Owner would technically provide sufficient access but violates least privilege because it grants comprehensive resource-management permissions, including access-control authority far beyond monitoring.

Because the administrator's duties are specifically monitoring-oriented but require configuration changes, Monitoring Contributor supplies the correct functional scope without granting unrestricted ownership.

Study Guide reference: Secure Oracle AI Database@Azure — Azure RBAC, monitoring permissions, least privilege and operational administration

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.

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