1z0-1147 Questions and Answers

Oracle Zero Downtime Migration organizes its Oracle database migration methods into two fundamental workflow families: Physical Migration and Logical Migration . Each family can then have online and offline variants depending on compatibility requirements and acceptable downtime.

Physical migrations operate on the physical database representation and rely on technologies such as RMAN and Oracle Data Guard. Physical Online migration can instantiate a target using Restore From Service and maintain synchronization using Data Guard, while Physical Offline uses RMAN backup and restore.

Logical migrations operate through logical database objects and data. Oracle Data Pump provides the initial export/import mechanism, while Logical Online migration integrates Oracle GoldenGate to capture and replicate ongoing transactions before cutover. Logical workflows are also suitable for many cross-version or cross-platform scenarios that physical workflows cannot support.

"Container-based migration" and "snapshot-based migration" are not ZDM's top-level migration workflow categories.

Oracle's current ZDM documentation explicitly states that ZDM supports both Physical and Logical Migration workflows.

Therefore, B and D are correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM workflow categories.

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

OCI Vault is Oracle Cloud Infrastructure's centralized service for managing encryption keys and secrets. In Oracle AI Database@Azure, it can participate in customer-managed key architectures for Oracle Transparent Data Encryption.

TDE encrypts Oracle database data at rest using master encryption keys. Oracle AI Database@Azure supports Oracle-managed keys stored in an Oracle Wallet as the default model and several customer-managed key stores, including OCI Vault, Oracle Key Vault, and Azure Key Vault. Using OCI Vault allows organizations to manage cryptographic key lifecycle operations—including controlled creation, rotation, access policy, and auditing—outside the database itself.

Vault and identity management should not be confused. Microsoft Entra ID and OCI IAM Identity Domains implement identity federation and user authentication; OCI Vault does not function as an identity provider. Likewise, it is unrelated to content delivery or application/network connectivity. Delegated subnets remain mandatory Azure networking constructs regardless of the selected encryption-key architecture.

Therefore, the correct description is A .

Study Guide reference: Secure Oracle AI Database@Azure — TDE, Oracle-managed and customer-managed encryption keys, OCI Vault.

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

Oracle's current onboarding documentation explicitly states that customers purchasing through the Public Offer (Pay As You Go) must create a new OCI tenancy during onboarding.

The Public Offer is purchased directly in Azure Marketplace without negotiating a contract with Oracle Sales. Billing occurs through Azure, usage can count toward Microsoft Azure Consumption Commitment, and customers can start or stop consumption without a predetermined usage commitment. However, the trade-off relevant to this question is that an existing OCI tenancy cannot be linked to a Public Offer.

The Private Offer is different. Private Offer customers negotiate commercial terms with Oracle and can either link an eligible existing OCI tenancy or create a new OCI tenancy during onboarding.

Bring Your Own License affects Oracle Database software licensing economics rather than defining the Marketplace onboarding path. Universal Credits is likewise an OCI commercial construct and is not the Public/Private Oracle AI Database@Azure offer selection being tested.

Therefore, B is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Public Offer, Private Offer and OCI tenancy requirements.

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

Oracle Database Autonomous Recovery Service supports Long-Term Retention (LTR) backups for organizations that need to preserve full database backups for compliance, regulatory, legal, or business requirements. The correct destination is the OCI Object Storage Infrequent Access tier .

The question source specifies that the LTR backup initially remains in the standard storage tier and transitions after the first 24 hours to Infrequent Access storage for the remainder of its retention period. Oracle's Recovery Service documentation independently confirms that long-term retention backups are stored in the Object Storage Infrequent Access tier and can be retained for periods extending up to ten years.

The Infrequent Access tier is appropriate because LTR backups are retained for extended periods but are generally restored less frequently than operational backups. Archive Storage is not the managed destination used by Recovery Service for this workflow. Azure Archive Blob Storage is likewise not the Oracle-managed OCI storage tier identified for these backups, and there is no "OCI Legacy Backup" storage tier.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous Recovery Service, LTR backups, retention and storage lifecycle.

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

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.

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

An Oracle AI Database@Azure delegated subnet remains part of the customer's Azure VNet and can use supported Azure networking controls. Two fundamental controls are Network Security Groups (NSGs) and Azure route tables containing User-Defined Routes .

An NSG performs traffic filtering by applying inbound and outbound security rules based on criteria such as source, destination, protocol, and port. This allows organizations to enforce database-access policies at the Azure network layer. Route tables provide forwarding control, allowing traffic to be directed through Azure Firewall, an NVA, a virtual network gateway, or other supported next-hop architecture.

Oracle's delegated-subnet design documentation explicitly states that because the delegated subnet belongs to the customer's VNet, it can leverage Azure networking capabilities including NSGs and routing tables . This enables private application-to-database communication while retaining enterprise routing and security controls.

Azure Load Balancer backend pools and Application Gateway ingress controllers are application/load-balancing constructs and are not the two subnet-associated controls identified for this Oracle database networking requirement.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet design, NSGs, Azure route tables, UDRs and traffic controls.

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

The correct staging medium is an Azure Files NFS share . Oracle's ZDM documentation for Autonomous AI Database Serverless on Oracle Database@Azure explicitly supports Azure Files as an NFS file-share source for Data Pump migration staging.

In the logical migration workflow, the NFS share is made accessible to the source database and attached to the Autonomous AI Database target. Data Pump export files can therefore be written to and read from the shared location without being staged in OCI storage. Oracle specifically documents mounting Azure Files NFSv4.x and exposing the path through a database directory for Data Pump operations.

OCI Object Storage and OCI File Storage would place the staging data within OCI, violating the explicit requirement that dump files remain in the Microsoft Azure subscription. Azure Blob Storage can be accessed by Autonomous Database through DBMS_CLOUD for supported object-storage workflows, but the standard ZDM NFS-based Data Pump staging mechanism described in this question uses a mounted filesystem rather than a direct Blob REST API.

Therefore, C is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM, Autonomous AI Database Serverless, Data Pump and Azure Files NFS.

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

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 Autonomous Container Database backup configuration includes an explicit backup-retention policy on termination . Administrators can select one of two supported behaviors: retain backups according to the normal configured backup-retention period, or retain them for 72 hours after termination and then delete them .

Oracle documentation identifies these options as RETAIN_PER_RETENTION_WINDOW and RETAIN_FOR_72_HOURS. The latter is the default in relevant API/Terraform configuration. Therefore, terminating an Autonomous Container Database does not inherently result in the immediate deletion of all automatic backups. Their post-termination lifetime is governed by the configured termination-retention policy.

Standard automatic backups are also not automatically converted into Long-Term Retention backups when the database is terminated. LTR backups have their own lifecycle and are explicitly excluded from the ordinary ACD termination-retention setting. No automatic export to Azure Blob Storage occurs as part of ACD termination.

Thus, B correctly reflects Oracle's documented post-termination backup behavior.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Container Database automatic backups, termination and retention policy.

For a cross-region Autonomous Data Guard standby , Oracle specifies a maximum possible data-loss objective of approximately 1 minute . Accordingly, the intended Recovery Point Objective is one minute.

Cross-region protection differs from a local Autonomous Data Guard standby because geographical distance makes fully synchronous zero-data-loss transport impractical for normal cross-region operation. Oracle therefore uses an asynchronous protection model that provides a bounded RPO while maintaining acceptable database performance.

A useful distinction is between RPO and RTO. RPO measures potential data loss, whereas RTO measures how long restoration of service is targeted to take. Oracle's current Autonomous AI Database Serverless SLO documentation continues to specify a 1-minute cross-region RPO . Current documentation has improved the cross-region RTO target to less than 10 minutes ; older material cited approximately 15 minutes. That RTO evolution does not affect the answer to this question because only RPO is being tested.

Zero data loss therefore applies to different protection scenarios, while five and fifteen minutes do not represent the documented cross-region RPO.

Study Guide reference: HA and DR — Autonomous Data Guard local and cross-region recovery objectives.

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

Oracle AI Database@Azure has specific client-subnet IP consumption requirements that must be considered during capacity planning. For the delegated client subnet, 13 IP addresses are reserved for networking services regardless of the number of VM Clusters deployed in that subnet .

Microsoft's Oracle AI Database@Azure networking documentation defines these 13 addresses as the first four addresses, the ninth through sixteenth addresses, and the final address of the subnet. Applied to 10.0.0.0/24, the reserved ranges are therefore 10.0.0.0–10.0.0.3, 10.0.0.8–10.0.0.15, and 10.0.0.255.

These platform reservations must be counted in addition to addresses needed for VM nodes and SCAN addresses. For example, every VM consumes multiple client-network addresses, and each VM Cluster requires SCAN addresses. Failing to account for the reserved block can therefore result in insufficient address capacity even when a subnet initially appears large enough.

Only option B precisely represents the documented reserved address positions.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet planning, client subnet sizing, reserved networking-service IP addresses and Exadata VM Cluster capacity.

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

The uploaded study set keys D , because it attempts to preserve data inside the same geographical region while obtaining a separate fault domain.

There is, however, an important current-documentation qualification. Oracle AI Database@Azure maps an OCI Availability Domain to an Azure Availability Zone , and Oracle MAA documentation describes local Data Guard standby deployments on another Exadata infrastructure in the same or a separate Azure Availability Zone . Oracle's cross-zone Data Guard implementation explicitly requires primary and standby Oracle AI Database@Azure deployments in two supported Azure AZs.

Therefore, option D is valid only if the second OCI Availability Domain corresponds to another supported Oracle AI Database@Azure Azure AZ. If the premise is literally that Oracle AI Database@Azure is available in only one Azure AZ and cross-region replication is prohibited, current Oracle documentation does not provide a second independent Oracle AI Database@Azure site simply by selecting an unmapped OCI AD.

For the uploaded question's intended key, the answer remains D , but the architecture should be treated with this deployment-availability condition.

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

Backup Retention Lock is a protection mechanism intended to prevent administrators or compromised credentials from prematurely reducing the recoverability window of Autonomous AI Database backups. Once the lock is established, normal administrative interfaces cannot simply disable it or reduce the protected backup-retention period.

Oracle's Autonomous AI Database documentation explicitly states that after the backup retention lock has been set, the option cannot be disabled or the retention period changed through ordinary database administration. To disable the lock or modify the locked retention setting, the administrator must file a Service Request with Oracle Cloud Support .

This design provides an administrative separation between ordinary database management and an action that could materially weaken backup protection. Changing an Azure Key Vault key has no relationship to the retention-policy lock. An SQL ALTER DATABASE command cannot override a service-level backup governance control, and the Azure Portal does not expose a supported bypass to reduce the locked period.

Accordingly, A is the only supported escalation path in the choices.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous AI Database backup protection, retention policy, retention lock and operational security controls.

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

The required workflow is ZDM Logical Online Migration . The defining requirements are cross-platform migration, database-version change, Data Pump initial loading, ongoing transaction replication, and minimal cutover downtime.

ZDM Logical Online uses Oracle Data Pump to establish the initial target data set and Oracle GoldenGate to capture and replicate transactions occurring on the source while the bulk migration is underway. Once the target is synchronized, ZDM coordinates the final cutover, reducing application interruption to the controlled switchover period.

This logical model is appropriate for migrations such as IBM AIX to Linux-based Exadata because logical migration is not dependent on source and target having identical physical database-file formats or endian architectures. It also accommodates supported cross-version migrations.

Logical Offline also uses Data Pump but does not maintain continuous GoldenGate synchronization and therefore requires substantially greater application downtime. Physical migration uses RMAN/Data Guard and is constrained by physical compatibility requirements, making it unsuitable for the described cross-platform transformation.

Thus, B is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM Logical Online, Data Pump and GoldenGate.

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

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.

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

Purchasing and subscribing to the Oracle AI Database@Azure Private Offer establishes the Azure Marketplace commercial relationship, but it does not complete the technical onboarding process. The next mandatory stage is linking the Azure subscription to an Oracle Cloud Infrastructure tenancy . Oracle refers to this process as multicloud linking.

For a Private Offer, the customer can either create a new OCI tenancy or link an existing eligible OCI tenancy. The linked OCI account supplies the Oracle-side control-plane context used for database resources, including management of container databases and pluggable databases and delivery of Oracle infrastructure and software maintenance services. Only after the Purchase and Link stages have been completed and the account relationship is verified can normal Oracle AI Database@Azure resource provisioning proceed.

Azure Key Vault integration is optional and relates to customer-managed TDE keys. Data Guard is configured after database infrastructure exists, and an Autonomous Database is not a prerequisite for Exadata.

Therefore, D is correct. Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Purchase, Link, Verify, and OCI tenancy association.

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

For an Autonomous AI Database Serverless target, Oracle Zero Downtime Migration supports Logical Online and Logical Offline migration workflows.

Logical migration is necessary because Autonomous AI Database Serverless abstracts the underlying physical database infrastructure and does not expose the file-system and database-host control required for a conventional physical RMAN/Data Guard migration. ZDM therefore operates through logical database migration technologies.

Logical Offline uses Oracle Data Pump export and import to instantiate the target. Logical Online adds Oracle GoldenGate to the workflow so changes occurring on the source after the initial data load are captured and applied to the target until final cutover, greatly reducing application downtime.

Oracle's Oracle Database@Azure migration documentation explicitly lists these two workflows for migration to Autonomous Database Serverless. Physical Online and Physical Offline workflows apply to supported customer-managed Oracle database targets, such as Exadata Database Service, rather than Autonomous Serverless.

Therefore, A is correct.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — Autonomous AI Database Serverless migration workflow support.

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

For Oracle AI Database@Azure's documented Azure-to-OCI federation architecture, Microsoft Entra ID functions as the enterprise identity provider. Oracle's reference architecture explicitly states that Microsoft Entra ID provides federated identity and access management for Oracle AI Database@Azure.

The OCI IAM Identity Domain remains an essential component because it is the Oracle-side service provider and identity domain that trusts the Microsoft Entra identity provider. However, when the question asks which platform provides the federated corporate identity in the Azure-integrated architecture, the answer is Microsoft Entra ID.

Oracle's onboarding instructions configure an Oracle Cloud Infrastructure Console enterprise application in Entra ID and then configure the OCI identity domain with Microsoft Entra ID as its SAML identity provider. Administrators can subsequently use their corporate Entra credentials for SSO into OCI when Oracle-native management tasks require it.

AD FS represents an older on-premises Microsoft federation service, while Okta is a third-party identity platform rather than the natively documented Azure integration.

Therefore, A is correct.

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

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

Oracle owns and operates the underlying Exadata infrastructure layer used by Oracle AI Database@Azure, even though that infrastructure is physically located in Microsoft Azure data centers. Consequently, Oracle performs infrastructure-level maintenance, patching, security updates, monitoring, and lifecycle operations.

Oracle-managed Exadata infrastructure components include the physical database-server hosts, storage servers, network fabric, hypervisor or virtualization infrastructure, firmware, management components, and control-plane systems. Microsoft supplies the Azure data-center environment and associated Azure platform capabilities, but Microsoft support engineers do not maintain Oracle's Exadata hardware/software stack.

The customer retains responsibility for customer-controlled portions of co-managed database environments, including database configuration and, depending on service and maintenance model, guest VM, Grid Infrastructure, database homes, and database software lifecycle activities. Oracle has also introduced optional Oracle-managed database software update capabilities for applicable newer Exadata services, but that does not change responsibility for the underlying infrastructure.

Therefore, C correctly identifies Oracle's Cloud Infrastructure operations organization.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — shared operational responsibility and Exadata infrastructure maintenance.

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

Oracle Zero Downtime Migration is Oracle Maximum Availability Architecture's recommended orchestration framework for moving Oracle databases while minimizing production interruption. For physical online migration , ZDM uses Oracle Data Guard. The target database is instantiated as a physical standby, redo generated on the source is transported and applied to the target, and ZDM coordinates the eventual switchover. Oracle documentation for Oracle Database@Azure specifically states that physical online migration uses direct data transfer, Restore From Service, and Oracle Data Guard to keep source and target synchronized.

For logical online migration , the underlying synchronization technology is Oracle GoldenGate. Oracle Data Pump provides the initial logical export/import, after which GoldenGate captures ongoing source transactions and applies them to the target until cutover. This workflow can also accommodate scenarios involving different database versions or platforms.

Oracle Sharding is an application/data-distribution architecture rather than ZDM's replication mechanism. Far Sync is a Data Guard component for specialized zero-data-loss configurations but is not the primary technology identified for ZDM migration orchestration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM physical online migration, logical online migration, Data Guard, GoldenGate, Data Pump.

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

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's Multicloud Architecture Framework emphasizes architectural considerations that arise because workloads, applications, data, identities, and operational responsibilities span multiple cloud providers. Two major areas are network latency/data movement and security, identity, and operations management .

Cross-cloud network latency can directly affect application response time, database performance, replication behavior, and transaction processing. Data movement can also introduce throughput constraints and cost considerations. Oracle therefore recommends workload placement and private connectivity strategies that minimize unnecessary cross-cloud distance and traffic.

Security and operations become similarly important because each cloud provider has its own IAM, monitoring, automation, and administrative models. Oracle recommends consistent identity and access policies, unified visibility, standardized automation, and common operational practices to avoid fragmented governance or management silos.

Hardware manufacturing origin and OCI hypervisor patch schedules do not represent the principal multicloud architectural design considerations described by the framework. Hypervisor maintenance is primarily a provider operational responsibility.

Therefore, B and D align directly with Oracle's documented multicloud design pillars.

Study Guide reference: Introduction to Multicloud — latency, data movement, Cloud Security, Cloud Operations, identity integration and operational standardization.

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

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.

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

The native architecture is to configure Azure Monitor diagnostic settings on the Oracle Exadata resources and route the selected log categories into an Azure Log Analytics workspace .

Oracle AI Database@Azure exposes relevant Exadata lifecycle and operational events through Azure diagnostic settings without requiring agents to be installed on Oracle-managed Exadata nodes. Once the telemetry reaches Log Analytics, administrators can query it using Kusto Query Language (KQL) and correlate the Oracle resource events with telemetry generated by Azure application infrastructure.

This architecture satisfies the requirement for centralized Azure-side observability while preserving the managed-service boundary of Exadata. It also integrates naturally with Azure dashboards, alerting, Microsoft Sentinel, and other Azure Monitor capabilities.

Using OCI Object Storage would introduce an unnecessary cross-platform telemetry pipeline. Oracle Enterprise Manager remains useful in broader Oracle management scenarios but is not required for this native Azure integration. Installing Azure Monitor Agent directly on Oracle-managed Exadata infrastructure is neither necessary nor the documented implementation pattern.

Therefore, A provides the supported integrated monitoring architecture.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Azure Monitor, diagnostic settings, Log Analytics, KQL and Exadata observability.

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

Oracle recommends OCI Full Stack Disaster Recovery (Full Stack DR) for orchestrating disaster-recovery operations around Oracle Database@Azure deployments.

Oracle's reference architecture for local and regional Oracle Database@Azure standbys explicitly recommends Full Stack DR to orchestrate database switchover and failover operations . The service can coordinate ordered disaster-recovery plans instead of requiring administrators to manually perform every database and infrastructure transition during an incident or DR drill.

Oracle Data Guard remains the underlying database replication and role-management technology, while Full Stack DR provides the higher-level orchestration framework for executing coordinated transitions.

Azure Site Recovery is primarily designed for Azure VM and workload replication/recovery and is not Oracle's recommended database-role orchestration service. GoldenGate provides logical replication and data integration rather than end-to-end DR orchestration. Azure Traffic Manager performs DNS-based traffic distribution and can participate in application routing, but it does not execute Oracle database switchovers or failovers.

Therefore, B is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — Full Stack DR orchestration and Data Guard role transitions.

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