Practice Free 1z0-1147 Oracle AI Database@Azure Architect Professional Exam Questions Answers With Explanation

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.

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

Identity federation is optional in Oracle AI Database@Azure. Oracle states that most normal database operations can be performed through the Azure environment without federation. Federation becomes particularly useful when administrators must enter the OCI Console for Oracle-specific database management tasks and want to authenticate using their corporate Microsoft Entra ID credentials.

The uploaded study material also identifies the user-record requirement of a last name and valid email address. Oracle's current federation documentation provides a slightly more detailed rule: provisioning users into OCI requires First Name, Last Name and Display Name , plus Email Address when the OCI Identity Domain is configured to require email addresses . Legacy Oracle Database@Azure federation documentation states the last-name/valid-email requirement directly.

Federation does not replace the OCI tenancy. Oracle AI Database@Azure always requires an OCI tenancy—either an existing tenancy linked through a Private Offer or a new tenancy created during onboarding.

Therefore, A and B are the intended answers.

Study Guide reference: Secure Oracle AI Database@Azure — optional identity federation and user provisioning requirements.

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

Oracle Database Autonomous Recovery Service provides the specific capabilities required for multi-year database backup retention combined with immutability .

Oracle's Long-Term Retention capability allows a full database backup to be retained for up to ten years . This addresses regulatory requirements that exceed ordinary operational backup-retention windows. Recovery Service additionally supports Retention Lock , which prevents protected backups from being modified or deleted before the configured retention period expires. This provides a database-aware immutability mechanism suitable for ransomware, malicious-administrator, and compliance-protection scenarios.

Merely increasing a standard Object Storage backup retention value does not provide the same Recovery Service lifecycle, recoverability validation, protection-policy model, or database-specific retention locking. NFS likewise does not introduce a managed ten-year immutable recovery framework. Manual on-demand backups also fail to provide policy-enforced retention and introduce unnecessary operational risk.

The combination of Recovery Service, LTR, and Retention Lock directly addresses both requirements in the question: ten-year retention and immutability .

Therefore, B is correct.

Study Guide reference: Secure Oracle AI Database@Azure — Autonomous Recovery Service, Long-Term Retention and Retention Lock.

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

Oracle AI Database@Azure has a default regional service limit of five delegated subnets . Once a deployment requires more than five delegated subnet links in a region, the customer must request a service-limit increase.

This aggregate regional limit must not be confused with the separate VNet design rule. An individual Azure VNet can contain a maximum of one delegated subnet for Oracle AI Database@Azure, but an organization can have several VNets and therefore several delegated subnets across the same region up to the default service limit.

Oracle identifies the relevant service-limit metadata as:

Service: Multicloud

Resource: Delegated Subnet Multicloud Links

Limit name: azure-delegated-subnet-count

The limit operates at regional scope. Therefore, creating additional peerings or Route Servers does not bypass it; the correct approach is to request additional service capacity through Oracle's service-limit process.

Values of 1, 3, and 10 do not represent the default regional limit.

Therefore, A. 5 is correct.

Study Guide reference: Configure Oracle AI Database@Azure Networking — delegated subnet quotas and service-limit increases.

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

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.

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

Logical Online Migration combines an initial logical data load with Oracle GoldenGate change data capture to minimize production downtime.

The initial target database is populated using Oracle Data Pump export and import. Because that data movement can take a substantial amount of time for large databases, Oracle GoldenGate continuously captures transactions committed on the source while the initial load is being performed. Those transactions are subsequently applied to the target, allowing the destination to converge with the production source while the application remains active.

When synchronization reaches the required state, ZDM orchestrates the final migration phases and application cutover. The downtime requirement is therefore concentrated around the final transition rather than the entire export/import window.

Logical Offline uses Data Pump without continuous GoldenGate synchronization. Physical Online uses RMAN-based target instantiation and Oracle Data Guard redo synchronization instead of GoldenGate. Physical Offline similarly relies on physical backup/restore processes and does not use logical change-data capture.

Thus, B. Logical Online Migration is correct.

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

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

When Oracle Autonomous AI Database Serverless is provisioned through Oracle AI Database@Azure, the administrative database account follows the standard Autonomous Database account model. The Azure creation workflow exposes the Username field as read-only and set to ADMIN .

The administrator therefore supplies the password for the predefined ADMIN account but does not choose or rename the account during database creation. Oracle currently specifies password requirements separately, including minimum and maximum length and character-composition requirements.

The account is not derived from the Microsoft Entra ID identity that deploys the Azure resource. Azure RBAC and Microsoft Entra authentication govern access to the Azure resource-management plane, whereas the ADMIN credential is a database-level account. Similarly, SYS is not presented as the configurable provisioning username for Autonomous AI Database Serverless, and the username is not generated from subscription metadata.

This separation between Azure control-plane identity and Oracle database credentials is architecturally important when designing authentication and administrative access.

Therefore, the correct answer is A .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database Serverless creation, configuration and administrator credentials.

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

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.

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

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.

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

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.

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

The Data Guard Observer is an independent process used by Fast-Start Failover to monitor the primary and standby databases and determine whether an automatic failover should occur. Because its independence directly affects the reliability of the failover decision, it should not share the same failure domain as either database.

For an Oracle AI Database@Azure architecture spanning availability zones, placing the Observer on a separate Azure VM in another availability zone provides appropriate fault isolation. If the primary AZ fails, the Observer remains available to verify the failure and initiate the transition to the standby. Hosting the Observer directly on the primary database node would cause it to disappear with a primary-site outage. Hosting it on the standby similarly creates an undesirable dependency on the standby environment.

The Observer is an external Data Guard Broker process; it does not belong inside Oracle's multicloud control-plane Parent Site. For stronger resilience, Oracle Data Guard can also support multiple observers in appropriate configurations.

Therefore, D represents the recommended architecture.

Study Guide reference: HA and DR with Oracle AI Database@Azure — Data Guard Broker, FSFO and Observer placement.

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

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 Exadata Database Service on Exascale Infrastructure is eligible for both the Private Offer and Public Offer , with the Public Offer representing the Pay As You Go marketplace model.

A Private Offer is negotiated with Oracle and can include custom pricing, contract terms, usage commitments, and enterprise commercial arrangements. After agreement, the customer accepts the private offer through Azure Marketplace.

A Public Offer allows supported Oracle AI Database@Azure services to be purchased directly from Azure Marketplace without first negotiating a private commercial agreement. Oracle describes this model as Pay As You Go, with no predetermined usage commitment. Oracle's current Azure service table explicitly lists Exadata Database Service on Exascale Infrastructure as eligible for both offer types.

Azure Reserved Instance pricing is an Azure compute purchasing construct and is not one of the Oracle AI Database@Azure offer mechanisms. Oracle also specifies that free-trial subscription models are not the purchasing path for these multicloud database resources.

Therefore, B and C are correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Public Offer, Private Offer and Exascale purchasing.

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

The administrator must use the OCI Console for database-management operations that remain exposed through Oracle Cloud Infrastructure. Oracle AI Database@Azure deliberately integrates many infrastructure lifecycle operations into Azure, but the service still maintains an associated OCI tenancy and OCI control plane. Consequently, certain Oracle-native operations—particularly detailed Container Database (CDB) and Pluggable Database (PDB) administration—require access to OCI.

The configured Microsoft Entra ID federation eliminates the need for a separate set of OCI credentials. Oracle documents federation as an optional capability that enables users to authenticate to the OCI tenancy by using their existing Microsoft Entra ID credentials. Oracle specifically notes that although most daily operations can be performed within Azure, some database-management tasks require OCI Console access.

Azure Cloud Shell operates Azure CLI/PowerShell workflows and is not the required CDB/PDB management interface. The Marketplace page controls purchasing and subscriptions, while a standalone Enterprise Manager installation is not the primary management portal for this service.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — OCI Console access and database lifecycle management.

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

Oracle Autonomous AI Database is specifically designed for workloads where elasticity and minimal administrative overhead are primary requirements. Oracle describes it as a fully autonomous, self-governing database service that handles provisioning, backups, patching, upgrading, performance management, and resource scaling without traditional database-administration effort.

For unpredictable workloads, compute auto scaling is particularly significant. When enabled, Autonomous AI Database can automatically consume additional CPU and I/O resources as workload demand rises without requiring an administrator to manually resize the database. Storage can likewise be scaled and can use separate auto-scaling functionality.

Exadata Database Service on Dedicated Infrastructure provides extremely high performance and consolidation capabilities but retains customer database-management responsibilities. Exascale Infrastructure improves Exadata's elastic infrastructure model but is still not equivalent to Autonomous Database's fully managed, self-governing operational model. Base Database Service similarly requires substantially more customer administration.

Therefore, a cloud-native application with volatile usage and a requirement for essentially zero database administration maps directly to Oracle Autonomous AI Database .

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Autonomous AI Database, elastic scaling, automated management and serverless operations.

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

The default encryption-key model for an Exadata database on Oracle AI Database@Azure is Oracle-Managed Keys (OMK) . Under this model, Oracle automatically generates the Transparent Data Encryption master encryption key and stores it in an Oracle Wallet secured within the database environment.

Oracle manages the complete lifecycle of this default key, including generation, secure storage, rotation, backup, and restoration. No additional customer-side key-management infrastructure is required.

OCI Vault, Oracle Key Vault, and Azure Key Vault represent customer-managed key alternatives. When an organization selects one of these mechanisms, the TDE master key is managed outside the local Oracle Wallet, enabling centralized customer control, auditing, rotation policy, and separation of duties. However, none is the default unless the customer explicitly configures a customer-managed key architecture.

Oracle's current security documentation explicitly identifies Oracle Wallet as the default encryption-key setting for Exadata Database Service on Oracle AI Database@Azure.

Therefore, C. Oracle Wallet is correct.

Study Guide reference: Secure Oracle AI Database@Azure — TDE, Oracle-managed keys and Oracle Wallet.

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

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 AI Database@Azure supports two broad TDE master-key management approaches: Oracle-managed keys and customer-managed keys .

With the default Oracle-managed model, the TDE master encryption key is generated and stored in an Oracle Wallet within the database environment. Oracle manages key generation, storage, rotation, backup, and restoration activities associated with this model.

For customer-controlled key management, Oracle supports several external key stores. For Exadata Database Service on Dedicated Infrastructure, these include Azure Key Vault , OCI Vault, and Oracle Key Vault. Azure Key Vault integration is particularly useful for organizations that want their database encryption-key governance aligned with existing Azure key-management, auditing, and separation-of-duties practices.

AWS KMS and Google Cloud KMS are not native key-management choices for an Oracle AI Database@Azure Exadata deployment.

Therefore, the two correct selections from this answer set are A and D .

Study Guide reference: Secure Oracle AI Database@Azure — Transparent Data Encryption, Oracle Wallet, customer-managed keys and Azure Key Vault.

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

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.

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

Purchasing the Azure Marketplace offer establishes the commercial entitlement, but it does not by itself establish the technical relationship between the customer's Azure environment and OCI tenancy. Oracle's onboarding sequence requires multicloud linking after purchase.

During this step, the selected Azure subscription is linked with an Oracle Cloud Infrastructure tenancy. That association enables the service to establish the required cross-cloud resource, subscription, governance, and management relationships. Oracle's current overview explicitly states that after the purchase is complete, the Azure subscription is linked with an OCI tenancy; this process is called multicloud linking.

Only after onboarding and linking are completed does the administrator move into resource provisioning. At that stage, the environment can be prepared with the VNet, delegated subnet, Exadata infrastructure, VM Cluster, Autonomous AI Database, or applicable anchor constructs. Therefore, creating networking components before completing the required subscription/tenancy association reverses the documented onboarding sequence.

DNS-specific configuration is also part of networking rather than the immediate post-purchase account-linking requirement.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Marketplace purchase, multicloud linking, Azure subscription-to-OCI tenancy association and provisioning prerequisites.

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

For ZDM physical online migrations using direct data transfer , Oracle's Maximum Availability Architecture pattern uses RMAN's Restore From Service capability. Rather than first creating backup pieces in a staging location, transporting them, and then restoring them on the target, RMAN restores the target database directly across the network from the source service.

This design reduces intermediate storage requirements and simplifies the migration pipeline. Once the target database has been instantiated, ZDM automatically configures Oracle Data Guard and uses redo transport to maintain synchronization until the planned switchover. The combination of Restore From Service and Data Guard is the central technical pattern Oracle documents for physical online migration to Exadata Database Service on Oracle AI Database@Azure.

Although DUPLICATE ... FROM ACTIVE DATABASE is a legitimate RMAN cloning capability in other contexts, it is not the named method documented for this ZDM direct-data-transfer workflow. Compressed backup-set streaming and incremental image-copy pushing also imply different backup/staging mechanisms.

Therefore, Restore From Service is the MAA-aligned RMAN method represented by the scenario.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — MAA, ZDM Physical Online migration, RMAN direct data transfer and Restore From Service.

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

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.

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

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.

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

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.

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

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.

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