1z0-1147 Oracle AI Database@Azure Architect Professional Questions and Answers

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.

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

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.

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

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.

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

During Exadata VM Cluster provisioning, the administrator selects the client delegated subnet and can explicitly provide a CIDR range for the Exadata backup network. If no backup-subnet CIDR is supplied, Oracle automatically uses the documented default of 192.168.252.0/22 .

The backup subnet serves Oracle database backup-network requirements and is architecturally distinct from the Azure delegated client subnet. Oracle's deployment-planning guidance emphasizes that the default backup CIDR is not part of the Azure VNet CIDR allocation. Nevertheless, address planning remains important. In disaster-recovery designs involving multiple Exadata deployments—especially cross-availability-zone or cross-region configurations—the administrator should explicitly choose non-overlapping backup CIDR blocks so that replication, routing, and backup traffic do not encounter conflicting address ranges.

Option B uses the correct network prefix but an incorrect /24 mask. Options A and D use different base networks and therefore do not match the Oracle provisioning default.

Accordingly, the correct response is C: 192.168.252.0/22 .

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata VM Cluster client and backup networks, CIDR planning, default backup-subnet configuration and non-overlapping network design.

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

The -eval option invokes the evaluation workflow of Oracle Zero Downtime Migration rather than executing the production migration. Oracle specifically directs administrators to use ZDMCLI migrate database ... -eval to evaluate the migration process, including prerequisite checks, source/target connectivity verification, configuration validation, and applicable pre-migration assessment phases.

The resulting job is an evaluation job rather than a migration job that performs database movement. This distinction is reflected throughout ZDM command handling: ZDM can query evaluation jobs separately from actual migration jobs, and the evaluation workflow is intended to identify prerequisite or configuration failures before production data movement begins.

The option does not create a mock standby or execute a simulated Data Guard switchover. It also does not begin an offline migration and stop before the copy phase. CPAT may participate in migration-readiness assessment depending on ZDM version and command options, but -eval is not an installation command for CPAT.

Consequently, A correctly represents the effect: an EVAL-type workflow performs migration prechecks and validation without executing the actual migration.

Study Guide reference: Migrate Oracle Databases to Oracle AI Database@Azure — ZDM CLI, evaluation mode, migration validation and prechecks.

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

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.

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

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.

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

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.

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

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 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.

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

Elastic resource allocation is a fundamental design characteristic of Oracle Exadata Database Service on Exascale Infrastructure . A VM requires a minimum of 8 enabled ECPUs at initial provisioning, but its compute allocation can subsequently be increased in 4-ECPU increments .

Oracle's Exascale architecture draws compute resources from Oracle-managed shared infrastructure rather than requiring the customer to purchase or provision dedicated database servers. This permits a customer to start with a relatively small footprint and increase capacity as workload requirements develop.

The workload therefore does not need to be migrated to Dedicated Infrastructure merely because additional processing power is required. Nor is it necessary to destroy and rebuild the VM Cluster or create an entirely new Exadata Infrastructure resource. Exascale is specifically intended to avoid those fixed-capacity operational patterns.

Oracle additionally supports online scaling of Exascale storage independently through the associated Database Storage Vault, reinforcing the service's elastic consumption model.

Therefore, D is correct.

Study Guide reference: Provision and operate Oracle AI Database@Azure Resources — Exascale elastic ECPU scaling.

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

Oracle's Hub-and-Spoke design guidance defines an important UDR rule for Oracle AI Database@Azure delegated subnets: the route prefix must be at least as specific as the delegated subnet CIDR . A /24 delegated subnet therefore cannot be reliably represented by a broader /16 route when the architecture requires the delegated subnet-specific path.

The less-specific route can fail to take precedence over more-specific system or service routes. This creates the possibility that traffic takes one route toward the database but returns through a different route. Such asymmetric routing is especially problematic with Azure Firewall or an NVA because stateful firewalls expect both directions of a connection to traverse the same inspection point. If the return packet follows a different path, the firewall can drop the session.

A UDR has no mechanism for duplicating VNICs, changing SQL*Net encryption, or resizing the underlying subnet. It simply influences Layer-3 forwarding.

Therefore, A accurately describes the documented routing consequence.

Study Guide reference: Configure Oracle AI Database@Azure Networking — UDR prefix specificity, delegated subnet routing, Hub-and-Spoke and asymmetric routing prevention.

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

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

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

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

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

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

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

The 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 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 AI Database@Azure applies stricter hostname-prefix validation than the generic 63-character DNS-label maximum. For an Exadata VM Cluster, Oracle's DNS and network-design documentation specifies a maximum hostname-prefix length of 23 characters .

The value also has syntactic constraints. It must begin with a letter, end with an alphanumeric character, and can contain hyphens. Certain reserved values are prohibited. These restrictions exist because the supplied prefix becomes part of system-generated host and database-network names; Oracle must reserve additional character capacity for generated suffixes and service-specific naming constructs.

Therefore, 63 characters represents a general DNS-label ceiling but is not valid for this Exadata field. Thirty characters likewise exceeds the Oracle-specific limit, while 15 characters is unnecessarily restrictive.

The correct maximum is consequently 23 characters .

This is a configuration detail worth memorizing because hostname validation occurs during VM Cluster provisioning and an invalid prefix can block resource creation before the underlying Exadata compute nodes are deployed.

Study Guide reference: Configure Oracle AI Database@Azure Networking — Exadata VM Cluster DNS, hostname prefix rules and naming constraints.

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

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'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.

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

Oracle's current Oracle AI Database@Azure service matrix explicitly identifies Oracle Exadata Database Service on Exascale Infrastructure as eligible for both Private Offer and Public Offer purchasing models.

A Public Offer uses a pay-as-you-go Azure Marketplace model and allows customers to begin consuming supported services without first negotiating a custom contract with Oracle Sales. A Private Offer is based on negotiated commercial terms and is appropriate for enterprise commitments and customized pricing.

Exadata Database Service on Dedicated Infrastructure is Private Offer eligible but not Public Offer eligible. The same Private-Offer-only restriction applies to Autonomous AI Database on Dedicated Exadata Infrastructure. Oracle Database Autonomous Recovery Service is a database protection service rather than the alternative primary high-performance Exadata database platform requested by the scenario, and it is also listed as Private Offer only.

Exascale therefore combines Exadata database capabilities with a lower-entry, elastic shared-infrastructure model and marketplace flexibility.

Thus, A is correct.

Study Guide reference: Oracle AI Database@Azure Architecture and Onboarding — Azure Marketplace offers and available database services.

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

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'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.

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

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.

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

Oracle's preferred ZDM Physical Online workflow for Oracle Database@Azure supports direct data transfer , specifically to avoid staging large RMAN backups in intermediate object or file storage. In this workflow, ZDM creates the target database using the Restore From Service method.

RMAN streams the required database blocks directly from the source database service to the target environment over the configured network connection. After the target database has been instantiated, Oracle Data Guard maintains synchronization between source and target by transporting and applying redo. ZDM then orchestrates the cutover when the migration reaches the appropriate stage.

This approach is particularly significant for a large database such as the 10 TB system in the scenario because intermediate backup staging would require substantial temporary storage, additional I/O, and backup-transfer operations. Oracle explicitly states that the physical online direct-data-transfer workflow creates the target through Restore From Service and avoids backing up the source to an intermediate storage location.

Backup and Restore therefore describes the physical offline/staged model. Transportable Tablespaces is not the standard ZDM physical-online instantiation mechanism.

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

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

Oracle Application Continuity (AC) is the application-availability technology designed to mask recoverable database outages and replay database requests transparently after a connection is re-established.

Oracle RAC provides database-service continuity when one database instance or node becomes unavailable, but an application may still have active sessions or in-flight work on the failed instance. Application Continuity works with Oracle's high-availability connection infrastructure, database services, FAN, Transaction Guard, and supported clients to reconnect to an available instance and replay eligible database requests. This significantly reduces the application errors that would otherwise be exposed during node failure or planned maintenance.

Fast-Start Failover and Data Guard Broker operate at the Data Guard database-role and disaster-recovery level. They manage primary/standby transitions rather than transparently replaying an individual application session after a RAC node failure. Transparent Data Encryption protects database data at rest and has no role in request replay or failure masking.

Therefore, C. Oracle Application Continuity is correct.

Study Guide reference: HA and DR with Oracle AI Database@Azure — RAC application availability, FAN, Transaction Guard and Application Continuity.

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

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.

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

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.

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