Exam Cloud Digital Leader topic 1 question 42 discussion

Agree with C, Compute Engine. From GCP documentation "For the workloads that will benefit from containers, Migrate for Anthos and GKE delivers a fast, smooth path to modernization. For other workloads that are better suited as a VM, simply move them as is with Migrate for Compute Engine "

I would choose D. Migrate the workloads using Migrate for Anthos, because it is similar to Question #43 and this is C. Migrate the workloads to Compute Engine. I agree with Tom666

Agree with C, I saw the documentation, it explains how to migrate VM to Compute Engine VM from GKE. let the link: https://cloud.google.com/migrate/containers/docs/migrate-vm

Migrate for Compute Engine to lift and shift VMs quickly

Migrate for Compute Engine (formerly known as Velostrata) is specifically designed for migrating VMs from on-premises environments (including hypervisors like VMware) to Google Compute Engine. It offers several key advantages for modernization:   Minimal Downtime: Migrate for Compute Engine streams application data to Google Cloud in the background while the application continues to run on-premises. This minimizes disruption during the migration process.   Flexibility: It supports both Linux and Windows VMs, covering your company's needs. Phased Approach: It allows you to migrate VMs in phases, giving you control over the migration process.   Modernization Path: While it initially lifts and shifts VMs, it sets the stage for future modernization efforts. Once the VMs are in Compute Engine, you can then start refactoring and containerizing applications as needed.

The correct answer is D. Migrate the workloads using Migrate for Anthos because it enables the modernization of workloads by converting virtual machines (VMs) into containers, which aligns with cloud-native technologies. Why not the other options? A. Export the VMs into VMDK format, and import them into Compute Engine – This approach moves VMs to Google Cloud but does not modernize them into cloud-native technologies. B. Export the VMs into VMDK format, and import them into Google Cloud VMware Engine – This maintains the existing hypervisor-based architecture rather than modernizing workloads into containers. C. Migrate the workloads using Migrate for Compute Engine – This service lifts and shifts VMs to Compute Engine but does not transform them into cloud-native workloads like containers.

keywords modernize and cloud native. So Anthos.

Compute Engine, Since there was no documentation given in terms of incompatibiliy

Migrate for Compute Engine is a service designed specifically for migrating existing virtual machines from on-premises environments directly to Google Cloud’s Compute Engine. This tool automates many aspects of migration, including replication of VM configurations and data transfer while minimizing downtime. It also supports both Linux and Windows servers, making it versatile for various workloads. Considering all factors—ease of migration, retention of existing workload functionality during transition, and alignment with modernization goals—the most effective choice would be:

The answer is in the question "modernize workloads as much as possible by adopting cloud-native technologies" What is Migrate for Anthos? Enter Migrate for Anthos, a fast and easy way to modernize your existing applications with a service that encapsulates them in a container. Moving your physical servers or existing VMs into Kubernetes containers gives you crucial portability and resource utilization benefits without having to rewrite the underlying application. Since Migrate for Anthos is built for Google Kubernetes Engine (GKE), you also automatically capture the scaling and flexibility benefits of a managed Kubernetes environment in the cloud

Compute Engine as it is more suitable for VMs. Anthos option is more suited for the Containers.

Correct Answer is : C. Migrate the workloads using Migrate for Compute Engine. Explanation: Migrate for Compute Engine is specifically designed to facilitate the migration of virtual machine workloads from on-premises environments to Google Cloud. It supports both Windows and Linux VMs and allows for seamless migration with minimal downtime. This service enables you to modernize your applications while maintaining their existing configurations, which aligns with your goal of transforming workloads into cloud-native technologies. Migrating the workloads using Migrate for Anthos (option D) is focused on containerized workloads and would not be applicable if the current workloads are primarily running on traditional VMs.

Agree with C

Google Cloud VMware Engine (GCVE) allows your organization to lift and shift its VMware-based workloads to Google Cloud with minimal changes. This approach lets you keep your existing virtualized environment (including your hypervisor) while running it on Google Cloud's infrastructure. This option also offers managed services for the VMware stack, allowing you to offload management tasks while still using a familiar environment. Why not the other options: B. Migrate the workloads to Compute Engine: Although Compute Engine allows you to run VMs in Google Cloud, it would require more changes to your existing environment compared to VMware Engine, and it's not fully managed in the same way as Google Cloud VMware Engine.

C. Migrate the workloads using Migrate for Compute Engine Here’s why this option is most appropriate: Migrate for Compute Engine: This service is designed specifically to facilitate the migration of on-premises VMs to Google Cloud Compute Engine. It automates the migration process, supports various operating systems (Linux and Windows), and helps you transition your VMs while allowing you to modernize your infrastructure and applications during the migration. This tool simplifies the migration of VMs and can also assist in optimizing the configurations for Google Cloud.

The best answer here is C. Migrate the workloads using Migrate for Compute Engine. Here's why: Migrate for Compute Engine is Google Cloud's managed service specifically designed for migrating on-premises workloads to Compute Engine. It provides a streamlined approach to lift-and-shift your existing VMs to Google Cloud while minimizing downtime and ensuring a smooth transition.

This Use Case fits very well with Compute engine - why using Anthos here (its core technology developed by Google empowering enterprise container platforms)? If anthos is solution, then you would have to be very creative in interpreting this question