Exam Cloud Digital Leader topic 1 question 53 discussion

B: Artifact Registry can manage container image migration and Cloud Storage can store virtual disk image

I'm voting for B, not A because Filestore is more user files oriented when Cloud Storage is the best choice for disk images. Artifact Registry (aka Container Registry) is THE storage service for container images.

B. Artifact Registry and Cloud Storage Here’s why: Artifact Registry: This service is designed to manage and store container images and other artifacts. You can use Artifact Registry to store and manage your container images, making it an ideal solution for migrating and managing your container workloads in Google Cloud. Cloud Storage: This service is suitable for storing and transferring large amounts of data, including virtual machine disk images. You can use Cloud Storage to upload and store VM disk images before importing them into Google Cloud's Compute Engine.

Compute Engine allows you to create and manage virtual machine instances, making it ideal for migrating virtual machine disks. Filestore, on the other hand, provides a managed file storage service that can be used to migrate container images. Therefore, option A (Compute Engine and Filestore) is the correct choice for migrating both container images and virtual machine disks to Google Cloud.

B is correct

Artifact Registry is a fully managed registry service for storing container images. Cloud Storage is a highly scalable object storage service. Together, they can be used to migrate container images from an on-premises environment to Google Cloud.

B is correct

Here are the reasons why the other options are not as good as Artifact Registry and Cloud Storage for migrating container images and virtual machine disks to Google Cloud: Compute Engine and Filestore are both compute services that can be used to create and run virtual machines. However, they do not provide a good way to store and manage container images. Dataflow and BigQuery are both data processing services. They can be used to process and analyze data, but they are not designed for storing and managing container images. Pub/Sub and Cloud Storage are both messaging and storage services. They can be used to store and transmit data, but they are not designed for storing and managing container images.

When migrating your containers and virtual machines to Google Cloud, you can utilize Artifact Registry and Cloud Storage to streamline the process and ensure a smooth transition. Artifact Registry can be used to store your container images as "golden images." These are pre-configured and optimized container images that serve as a starting point for deploying your containers in Google Cloud. You can push your golden images to Artifact Registry, where they will be securely stored and versioned. This allows you to easily manage and track different versions of your container images. On the other hand, Cloud Storage can be used to store your virtual machine disk images, which can also be considered as "golden images." These disk images contain the operating system and pre-installed software configurations that you want to use for your virtual machine instances. By uploading these disk images to Cloud Storage, you can ensure their availability and accessibility during the migration process.

B is the answer. Migration of your container images includes the following steps: Set up prerequisites. Identify images to migrate. Search your Dockerfile files and deployment manifests for references to third-party registries Determine pull frequency of images from third-party registries using Cloud Logging and BigQuery. Copy identified images to Artifact Registry. Verify that permissions to the registry are correctly configured, particularly if Artifact Registry and your Google Cloud deployment environment are in different projects. Update manifests for your deployments. Re-deploy your workloads.

https://cloud.google.com/compute/docs/import/importing-virtual-disks#bootable, It says to import the virtual disks to cloudstorage. THen only it is migrated to compute engine

Answer is A. Migrate for Compute Engine is how to migrate. B has to do with managing and storage, not migration.

refer to link https://cloud.google.com/compute/docs/import/import-existing-image and check the overiview section point no 4 which says "Upload the image file to Cloud Storage and import the image to Compute Engine as a new custom image."

The point is that you want to run it in GCP after migrating, not only manage the resources...?

It's B: Artifact Registry can manage container image migration and Cloud Storage can store virtual disk image

B.migrate container image: container registry, migrate vm disk: cloud storage.

Its B because it's about the container images and the virtual machine disks