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

Oracle AI Database@Azure integrates its operational telemetry with Azure Monitor diagnostic settings so organizations can apply existing Azure observability, compliance, and SIEM architectures to Oracle database infrastructure.

Three standard destinations are relevant here. An Azure Log Analytics workspace receives telemetry for centralized querying, dashboarding, alerting, and Kusto Query Language analysis. An Azure Storage account can archive logs or metrics for retention, compliance, or later processing. Azure Event Hubs provides a streaming destination for forwarding telemetry to SIEM products, custom consumers, event-processing pipelines, or other downstream platforms.

Oracle's Oracle AI Database@Azure monitoring documentation specifically lists Log Analytics Workspace, Storage Account, and Event Hub among the available Azure Monitor diagnostic-routing destinations. Oracle Enterprise Manager can monitor Oracle environments but is not an Azure Monitor diagnostic-settings destination. OCI Object Storage is likewise not selected directly as a destination from the Azure diagnostic-settings workflow. Azure SQL Database is a database service rather than a supported diagnostic sink.

Therefore, the three correct selections are A, C, and D .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — monitoring, Azure diagnostic settings, Log Analytics, Storage accounts and Event Hubs.

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

Oracle documents a specific 404 NotAuthorizedOrNotFound condition that can occur during Exadata VM Cluster creation when the selected private DNS zone does not already contain tags. Oracle then attempts to generate the default OCI oracle-tags, but the multicloud service principal must have permission to use the associated tag namespace.

The required policy statement is:

Allow any user to use tag-namespaces in tenancy where request.principal.type = 'multicloudlink'

Oracle's current troubleshooting guidance also requires the companion permission:

Allow any user to manage tag-defaults in tenancy where request.principal.type = 'multicloudlink'

The crucial detail is that the provisioning operation executes under the multicloudlink principal type , not an ordinary administrator group or a principal with request.user.id='multicloud'. Merely granting inspect permission is insufficient because the service must actually apply the tag namespace/defaults.

Thus, among the supplied options, C is the required policy statement.

Study Guide reference: Secure Oracle AI Database@Azure — OCI IAM, MulticloudLink service principal and tagging permissions.

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

Oracle Autonomous AI Database Serverless documents a local Autonomous Data Guard standby RTO SLO of two minutes for failure events that require failover to the standby.

For the Recovery Point Objective, current Oracle documentation is slightly more precise than the wording in option A: the local standby's maximum possible data-loss objective is less than 10 seconds . Therefore, the exam option stating "RPO of 10 seconds" represents the intended and closest supported value.

These SLOs apply to events such as full database failure, complete storage failure, corruption scenarios requiring standby transition, and availability-domain failures when Autonomous Data Guard is enabled. Local standby protection provides materially faster recovery and a substantially smaller possible data-loss window than cross-region standby protection because replication remains geographically close.

An hour-long RTO is inconsistent with active standby protection, while five-minute RPO and thirty-second RPO values do not match Oracle's stated local Autonomous Data Guard objectives.

Therefore, A is correct, interpreted technically as 2-minute RTO and < 10-second RPO .

Study Guide reference: HA and DR — Autonomous Data Guard local standby SLOs.

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

The requirement is specifically to place backup recovery points outside the cloud that hosts the production database . Oracle identifies this as the Cross-Cloud Backups multicloud use case.

In a cross-cloud backup architecture, production data hosted in one cloud is backed up to a different cloud provider. Oracle describes this pattern as providing protection against failures, operational mistakes, attacks, or other incidents affecting the primary cloud. Because the secondary copy is located outside the original cloud environment, it also provides an additional isolation boundary that can satisfy organizational or regulatory requirements for off-site backups.

An application/database split-stack design solves a different problem: it places application and database tiers in different clouds to exploit provider-specific capabilities. Horizontal workload distribution spreads active workloads across providers, while production/development separation assigns lifecycle environments to different clouds. Neither inherently guarantees an independently located backup recovery point.

The scenario is therefore a direct match for Oracle's Cross-Cloud Backups pattern.

Study Guide reference: Introduction to Multicloud — Cross-Cloud Backups, resilience, data protection and provider diversification.

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

Oracle defines the Azure-resident Child Site as an extension of the associated OCI Parent Site rather than as an independently governed Azure database platform. The Oracle database infrastructure is physically deployed in an isolated area of an Azure data center, while Oracle retains operation and management responsibility for the Oracle hardware and database service stack. The Child Site is paired with a geographically corresponding OCI region containing the Oracle AI Database@Azure control plane.

The critical architectural principle is that the Child Site maintains the same security, management, resiliency, and performance profile as an OCI region. This design minimizes compliance discontinuities when regulated database workloads are placed physically in Azure. OCI control-plane services continue providing lifecycle management, availability engineering, security controls, and operational governance. Parent and Child Sites are also positioned geographically to address data-sovereignty, residency, and latency requirements.

Therefore, the architecture does not transfer database security governance wholesale to Azure Security Center, nor does it depend on customer on-premises gateways for policy synchronization. Oracle explicitly describes the Child Site as an extension of the Parent Site. Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Parent Site, Child Site, control-plane architecture, security and resiliency.

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

Oracle AI Database@Azure Network Anchors support DNS integration between Azure-side applications and OCI-side database networking. The two endpoint constructs used by Oracle DNS are the DNS forwarding endpoint and DNS listening endpoint .

For inbound DNS resolution from OCI toward Azure, Oracle's Network Control Plane can create a forwarding DNS endpoint and configure forwarding rules so OCI-hosted resources can forward queries toward the Azure DNS environment. Conversely, outbound resolution from Azure toward Oracle resources relies on an OCI listening DNS endpoint. The listening endpoint receives DNS requests and enables Azure or connected on-premises systems to resolve Oracle AI Database@Azure names.

The terminology is important. Oracle explicitly uses listening and forwarding endpoint constructs. "DNS replication endpoint" is not the endpoint name used for private-zone synchronization, and "DNS peering endpoint" is not an Oracle Network Anchor endpoint type. DNS-record synchronization is a separate behavior from the endpoint resource itself.

Consequently, the correct selections are A and D .

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

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

Oracle's current network guidance defines two important delegated-subnet constraints. First, each Azure VNet can contain a maximum of one Oracle AI Database@Azure delegated subnet . Second, a single delegated subnet can support multiple VM Clusters , provided IP capacity and availability-zone constraints are satisfied.

Oracle clarifies that multiple VM Clusters from the same Exadata Infrastructure can share a delegated subnet. VM Clusters belonging to different Exadata Infrastructure resources can also share one when those infrastructure resources reside in the same availability zone .

However, Exadata Infrastructure resources located in different availability zones cannot share the same delegated subnet. Oracle identifies such a configuration as producing a suboptimal network path and requires separate delegated networking for cross-zone deployments.

The delegated subnet also uses Azure private address space; it is not required to use—and should not be designed around—a public IPv4 CIDR range.

Therefore, A and C are correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated-subnet limits, VM Cluster placement and IP addressing.

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

The requirements map directly to ZDM Physical Online Migration . A physical workflow uses RMAN-based database instantiation rather than Data Pump logical export/import. For online migration, ZDM combines physical target creation with Oracle Data Guard synchronization so redo generated after the initial database copy continues to be transported and applied to the target.

Because physical migration preserves the database at the block/file level, source and target compatibility requirements—including database version, platform characteristics, and character-set considerations—are more restrictive than with logical migration. The scenario explicitly states that the version and character set remain identical, which makes the physical workflow appropriate.

The online variant minimizes downtime because users continue operating against the source while target synchronization proceeds. Application interruption is concentrated around the final synchronization and switchover.

Logical Online instead uses Data Pump and GoldenGate. Physical Offline satisfies the RMAN requirement but introduces substantially longer downtime because the source cannot remain operational throughout migration.

Therefore, B is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Physical Online, RMAN and Data Guard.

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

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.

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

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.

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