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!
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise is planning to migrate 150 steady-state on-premises Windows Server and Red Hat Enterprise Linux (RHEL) workloads to Google Cloud Compute Engine. The financial operations (FinOps) team is conducting a Total Cost of Ownership (TCO) analysis to compare license-included (Pay-As-You-Go) images against custom-licensed (Bring Your Own License) options.
Which architectural and financial consideration correctly guides their migration strategy?
Multi-tenant Compute Engine instances require license-included (PAYG) per-vCPU billing for Windows Server, whereas BYOL for Windows Server requires deploying onto Sole-Tenant nodes where existing core-based licenses can be utilized.
License-included Linux distributions such as RHEL cannot be discounted under committed use contracts and must always remain on on-demand hourly pricing.
Sole-Tenant nodes strictly require purchasing Google-provided Pay-As-You-Go licenses for all provisioned vCPUs and prohibit reusing existing enterprise agreements.
Multi-tenant Compute Engine instances support Windows Server BYOL by applying existing customer product keys directly to standard VM instances without dedicated hardware.
Multi-tenant Compute Engine instances require license-included (PAYG) per-vCPU billing for Windows Server, whereas BYOL for Windows Server requires deploying onto Sole-Tenant nodes where existing core-based licenses can be utilized.
In Google Cloud, Compute Engine offers two primary licensing pathways for enterprise operating systems like Windows Server: standard license-included (Pay-As-You-Go / PAYG) images running on shared multi-tenant infrastructure, and Bring Your Own License (BYOL) deployed onto dedicated Sole-Tenant nodes.
This distinction is fundamental to accurate cloud cost modeling. Trying to use BYOL for Windows Server on shared multi-tenant VMs violates platform capabilities and vendor agreements, making Sole-Tenant nodes the necessary architectural pattern for BYOL while multi-tenant VMs serve as the standard PAYG target.
License-included Linux distributions such as RHEL cannot be discounted under committed use contracts and must always remain on on-demand hourly pricing.
Sole-Tenant nodes strictly require purchasing Google-provided Pay-As-You-Go licenses for all provisioned vCPUs and prohibit reusing existing enterprise agreements.
Multi-tenant Compute Engine instances support Windows Server BYOL by applying existing customer product keys directly to standard VM instances without dedicated hardware.
StudyCerts
StudyCerts