1z0-1123-25 Oracle Cloud Infrastructure 2025Migration Architect Professional Questions and Answers

You can run a cloud premigration advisor tool to perform compatibility check prior to migration

During physical migration, copies of database objects are created in dumps

Source and Target database versions must be the same

You cannot filter and migrate database objects

You cannot achieve zero or near-zero downtime with physical migration

vSphere Distributed Resource Scheduler (DRS)

OCI Fault Domain

vSAN Fault Domain

HCX Mobility Groups

To create a backup from the existing Migration Plan, as a precautionary measure against misconfiguration

To validate different compute shapes for each VM ensuring the most effective configuration can be chosen

To incrementally increase the allocated budget for each Migration Plan

To accelerate the migration task by assigning each Migration Plan to the respective migration team

It must be located in a different region than the source file system

Only a file system that has been exported can be used as a target file system

It must not have been previously exported

It must be located in the same availability domain as the source file system

Each subnet within a VCN employs multiple route rules, allowing for diverse routing paths based on traffic priorities

A subnet in a VCN is associated with a single route table, dictating how outbound traffic from all Virtual Network Interface Cards (VNICs) within that subnet is directed

If no route rule matches the network traffic you intend to route outside the VCN, the traffic is sent to the Internet

VCN local routing necessitates manual configuration of route rules to facilitate infrastructure communication

To perform real-time data compression and deduplication of the source data to be transferred to OCI

To serve as a temporary storage buffer to cache data before it is transferred to OCI

To facilitate direct VPN connectivity between the on-premises data center and OCI

To discover on-premises workloads and provide detailed inventory information to OCI

Is a remote virtual appliance deployed in the on-premises environment for discovery purposes

Represents a repository within OCI where migrated assets are temporarily stored before being deployed into their final configuration

Consists of credentials and connectivity details required by OCM to access and communicate with the on-premises environment

Provides real-time cost analysis and optimization recommendations for assets during the migration planning phase

The company can bring their own product licenses (BYOL) for VMware products such asvSphere, vSAN, and NSX

The company can move those application VMs into OCVS "as-is"

The company can control root access to the OCVS environment

The company can free up their IT team as Oracle takes over the management, including updates and patching of the OCVS environment

The company could convert all of VMware-based applications into native OCI Compute instances

Serverless

Base Database

Exadata Database on Dedicated Infrastructure

Dedicated Exadata Infrastructure

At both the Primary and Standby DR Protection Groups

DR Plans are automatically generated and cannot be created manually

Only at the Standby DR Protection Group

Only at the Primary DR Protection Group

HCX vMotion

HCX OS Assisted Replication

HCX Replication Assisted vMotion

HCX Bulk Migration

A Compute instance is automatically launched after the replication process

Deploy a Resource Manager Stack to launch the Compute instance with the replicated Block Volume

Create a Compute instance with an attached Block Volume and configure the Hydration Agent to transfer the replicated data into the Block Volume

Both HCX Manager and HCX Connector are deployed in the OCVS environment to facilitate bidirectional migrations between cloud instances

The HCX Manager is installed in the source environment to initiate migrations, whereas the HCX Connector receives the migration traffic in the target OCVS environment

The HCX Manager is deployed in the OCVS environment as the Tunnel receivers, whereas the HCX Connector is installed in the on-premises environment as the Tunnel initiators

The HCX Connector is responsible for WAN optimization and network extension in the OCVS environment, whereas the HCX Manager handles these tasks in the on-premises environment