An enterprise is planning to migrate a tier of interdependent application servers hosted on on-premises VMware vSphere virtual machines (VMs) to Compute Engine on Google Cloud. The migration team has identified the following technical requirements: Interdependent VMs supporting the application must be organized and migrated together in coordinated batches. The application's functionality and automated OS adaptations must be verified in Google Cloud without interrupting active production traffic on-premises. Production downtime during the final switchover must be kept to a minimum. Which migration approach and tooling should the enterprise implement?

Install the Migrate Connector in the VMware environment, organize the interdependent VMs into migration groups using Migrate to Virtual Machines, validate functionality with test clones in an isolated VPC during background replication, and execute cutover during a scheduled maintenance window.: ### What Migrate to Virtual Machines Is **Migrate to Virtual Machines** (formerly Migrate for Compute Engine) is Google Cloud's native, fully managed service designed to replicate and rehost physical servers and virtual machines from on-premises environments (such as **VMware vSphere**) or other public clouds directly into **Compute Engine**. ### How It Meets the Requirements - **Coordinated Batches via Groups**: Migrate to Virtual Machines allows administrators to organize interdependent VMs into logical units called **groups**. Operations across the entire VM migration lifecycle—such as replication, testing, and cutover—can be orchestrated collectively across the group to ensure multi-tier application consistency. - **Risk-Free Pre-Migration Validation**: During continuous background disk replication, the tool supports creating **test clones** in an isolated Virtual Private Cloud (VPC) sandbox. This enables operations teams to thoroughly test workloads, networking, and automated **OS adaptations** without disrupting active source VMs or on-premises production traffic. - **Minimal Downtime Cutover**: Data replication occurs continuously in the background. When the team is ready to complete the transition, a brief cutover window stops the source VM, synchronizes final delta changes, and starts the production Compute Engine instance. ### Key Advantages and Capabilities - **Automated OS Adaptations**: Automatically modifies drivers, boot configurations, and guest environments for seamless operation on Compute Engine. - **Non-Disruptive Background Replication**: Continuously streams storage changes without degrading on-premises application performance. - **Repeatable Test Cycles**: Allows teams to create and destroy test clones multiple times to validate configuration fixes before cutover. - **Centralized Management**: Integrates directly into the Google Cloud console with support for granular IAM controls and Cloud Monitoring. ### Why This Is Optimal This approach provides an end-to-end, structured lifecycle for lift-and-shift migrations. By leveraging **test clones** and **migration groups**, teams eliminate operational risk and reduce the final cutover duration to minutes rather than hours.

StudyCerts

Migrate Vmware Vms Compute Engine Test Clones | Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam! | StudyCerts

Professional Cloud Architect

Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Migrate Vmware Vms Compute Engine Test Clones

Section: Data and system migration and management tooling

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

An enterprise is planning to migrate a tier of interdependent application servers hosted on on-premises VMware vSphere virtual machines (VMs) to Compute Engine on Google Cloud. The migration team has identified the following technical requirements:

Interdependent VMs supporting the application must be organized and migrated together in coordinated batches.
The application's functionality and automated OS adaptations must be verified in Google Cloud without interrupting active production traffic on-premises.
Production downtime during the final switchover must be kept to a minimum.

Which migration approach and tooling should the enterprise implement?

Establish a hybrid connection with VMware HCX, execute cold migrations of individual VMs directly to Compute Engine, and perform post-migration testing after source instances are decommissioned.

Extract container artifacts from the VMs using Migrate to Containers, deploy the workloads into Google Kubernetes Engine (GKE) Autopilot, and mirror live network traffic between the data center and GKE to validate application logic.

Install the Migrate Connector in the VMware environment, organize the interdependent VMs into migration groups using Migrate to Virtual Machines, validate functionality with test clones in an isolated VPC during background replication, and execute cutover during a scheduled maintenance window.

Use Migration Center to perform live cutover of the source VMs into Compute Engine Managed Instance Groups (MIGs), and configure automated rollback scripts to restore source workloads if health checks fail.

Professional Cloud Architect

Migrate Vmware Vms Compute Engine Test Clones

Related questions