Your company is running the majority of its workloads in a co-located data center. The workloads are running on virtual machines (VMs) on top of a hypervisor and use either Linux or Windows server editions. As part of your company's transformation strategy, you need to modernize workloads as much as possible by adopting cloud-native technologies. You need to migrate the workloads into Google Cloud.
What should you do?
The primary goal mentioned in the question is to modernize workloads as much as possible by adopting cloud-native technologies. Migrate for Anthos is specifically designed to modernize applications by migrating them into containers and leveraging container orchestration with Google Kubernetes Engine. This approach aligns well with the goal of adopting cloud-native technologies, as it involves containerizing the workloads and managing them with Kubernetes, which are hallmarks of modern cloud-native architecture. Therefore, the best approach for modernization and adopting cloud-native technologies is to use Migrate for Anthos.
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 "
But, right, it says "cloud-native" and "modernize", so probably Migrate for Anthos is correct.
You can directly migrate VM loads to Anthos. It is a 2 step process
but as per i saw a official video google virtual machine migration need vSphere. https://cloud.google.com/migrate/virtual-machines?utm_source=bing&utm_medium=cpc&utm_campaign=japac-IN-all-en-dr-bkws-all-pkws-trial-b-dr-1009882&utm_content=text-ad-none-none-DEV_c-CRE_-ADGP_Hybrid%20%7C%20BKWS%20-%20PHR%20%7C%20Txt%20~%20Compute%20~%20Migrate%20for%20Compute%20Engine_migrate%20for%20compute%20engine-general%20-%20Products-KWID_43700071936703088-kwd-74698340556763%3Aloc-90&userloc_149209-network_o&utm_term=KW_google%20migrate%20for%20compute%20engine&gclid=3967b163c3031bcea7a9d442d7d20982&gclsrc=3p.ds
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
Difference between option C & D based on Purpose and Focus: Migrate for Anthos: This solution is focused on modernizing and migrating applications to containers and Kubernetes. It helps you containerize and manage your workloads using Google Kubernetes Engine (GKE) and provides a path to adopting cloud-native technologies. Migrate for Compute Engine: This solution is designed for straightforward lift-and-shift migrations of virtual machines (VMs) from on-premises or other clouds to Google Compute Engine (GCE) instances. In this question it's specifically mentioned that you need to modernize workloads as much as possible by adopting cloud-native technologies. Hence, I feel Anthos is a better choice here.
By using Migrate for Compute Engine, you can seamlessly migrate your Linux or Windows server edition VMs from your co-located data center to Google Cloud. This service provides automated migration capabilities, including replication, testing, and cutover, to ensure a smooth transition of your workloads. It also offers features like continuous data replication and minimal downtime during the migration process. Option D (migrating workloads using Migrate for Anthos) is more focused on modernizing applications by containerizing them and leveraging Kubernetes. While it is a valid option for certain scenarios, it may require additional effort to containerize your workloads and might not be the most straightforward approach for VM migration.
Migrate for Anthos is designed for migrating containerized applications, not VMs. It wouldn't be suitable for your current VM-based workloads. Therefore, Migrate for Compute Engine is the most suitable choice for your scenario. It enables you to migrate your VMs to Google Cloud while also modernizing them with cloud-native technologies, minimizing disruption and automating the process for a smooth and efficient transition.
Migrate for Anthos - migrate to containers Migrate for Compute Engine - migrate to VM these are the two options. Here it says VM, so C is right answer
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
Selected answer C
Migrate by Compute Engine
Migrate for Compute Engine is a service provided by Google Cloud that allows you to migrate your existing virtual machines (VMs) from on-premises or other cloud environments directly into Compute Engine. It provides a seamless migration experience, allowing you to retain your VM configurations and data while taking advantage of the scalability and flexibility offered by Google Cloud. This approach will help you adopt cloud-native technologies and modernize your workloads effectively.
The correct option is C.
C is correct because Migrate for Compute Engine is a service specifically designed to migrate VMs from on-premises environments or other clouds into Compute Engine. It provides automated migration capabilities and allows for the modernization of workloads during the migration process. D is incorrect because Migrate for Anthos is focused on migrating workloads into Google Kubernetes Engine (GKE) or Anthos clusters, which are container-based environments. It may not be suitable for migrating traditional VM-based workloads.
D is correct
D is correct
Migrate for Anthos uses a container-based approach to migration. It packages your workloads into containers and then deploys the containers to Anthos. This allows you to migrate your workloads to Google Cloud without having to make any changes to your workloads.
D is correct
i think since it has not mentioned anything related to Containerization or any upcoming plans for containerization, I think we can stick to C.also here it is also mentioned about the separate OS which we usually do on Compute engine.