Exam Professional Cloud Architect topic 1 question 194 discussion

Well, yes, you actually need a sole-tenant instance to install a windows server with your licence. A lot of links were pasted here, but after reading a lot of them, I reached this one who explicitly states: 'To create a VM instance that uses the custom BYOL image, you must provision the VM instance on a sole-tenant node.' https://cloud.google.com/compute/docs/images/creating-custom-windows-byol-images#use_the_custom_image

Sole tenant purpose is to facilitate importing licenses BYOL Sole-tenant nodes can help you meet dedicated hardware requirements for bring your own license (BYOL) scenarios that require per-core or per-processor licenses. When you use sole-tenant nodes, you have some visibility into the underlying hardware, which lets you track core and processor usage. To track this usage, Compute Engine reports the ID of the physical server on which a VM is scheduled. Then, by using Cloud Logging, you can view the historical server usage of a VM. To optimize the use of the host hardware, you can overcommit sole-tenant VM CPUs, share sole-tenant node groups and manually live migrate VMs.

Explanation: • To bring your on‐premises Windows Server 2022 licenses (BYOL) to Google Cloud, you must adhere to Microsoft’s licensing rules. • Microsoft requires that on-premises licenses used under License Mobility be deployed on sole-tenancy instances in Google Cloud. • Option D specifies importing the image with the proper OS flag (–os=windows-2022-dc-v) and launching a sole-tenancy instance, which is the correct procedure to utilize your existing licenses. This approach meets the licensing requirements while optimizing cost.

To create a VM instance that uses the custom BYOL image, you must provision the VM instance on a sole-tenant node.

No need to have a sole-tenancy instance

D is answer due to BYOL conditions of MS Mobility Licenses

A. is a valid and used strategy to migrate Windows Server virtual machines from an on-premises environment to Google Cloud Platform (GCP), especially when you want to carry over existing licenses using the Bring Your Own License (BYOL) approach.

To create a VM instance that uses the custom BYOL image, you must provision the VM instance on a sole-tenant node.

It shouod be c

Answer is A: Steps: 1 - Export an existing VM in .OVA format 2 - Install and Authorize the gCloud SDK 3 - Copy the .OVA file to a Google Storage Bucket 4 - Import the .OVA file to Google Cloud from the bucket. https://www.youtube.com/watch?v=NG38am3Y8hM gcloud compute instances import gcpinstanename --os=windows-10-x64-byol

Eligible Products: License Mobility typically applies to Microsoft software such as SQL Server and other Microsoft applications, but it's important to note that Windows Server licenses are generally not eligible for License Mobility. So, D.

Licensing scenarios such as licenses related to Linux BYOS with RHEL or SLES, as well as Microsoft applications don't require sole-tenant nodes. If you are considering bringing licenses from Microsoft applications such as SharePoint Server and SQL Server, use Microsoft License Mobility. https://cloud.google.com/compute/docs/nodes/bringing-your-own-licenses#importing_and_creating_an_image_from_an_offline_virtual_disk

either c or d but c seems right too

No need to have a sole-tenancy instance

https://cloud.google.com/compute/docs/import/importing-virtual-disks

D for sure with BOYL

If the customer truly wants to BYOL, then sole-tenant nodes are required which is a requirement for this question Yes it is required for BYOL because that's a requirement from Microsoft themselves https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud