Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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?
This option states that premium license-included Linux distributions (such as Red Hat Enterprise Linux and SUSE Linux Enterprise Server) are restricted exclusively to standard on-demand PAYG rates and cannot receive commitment-based cost reductions.
Google Cloud only allowed committed use discounts on core compute hardware (vCPU and RAM) while completely excluding software licensing fees.
When evaluating migration TCO, organizations should apply committed use discounts to both the compute infrastructure and eligible premium operating system license fees to achieve maximum financial efficiency.
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.
This option claims that Sole-Tenant nodes enforce Google-provided Pay-As-You-Go (PAYG) licensing for all virtual CPUs and do not permit customer-provided licenses.
Google Cloud did not offer dedicated host abstractions and only supported shared multi-tenant instances.
Organizations migrating large fleets of servers with active enterprise agreements often rely on Sole-Tenant nodes to prevent the substantial cost overhead of paying per-vCPU software licensing fees to cloud providers.
This option describes applying custom on-premises Windows Server licenses directly inside standard multi-tenant virtual machines via manual product key activation.
The workload were running specific customer application software with license mobility (such as certain SQL Server editions with active Software Assurance), but it is incorrect for the underlying Windows Server OS on multi-tenant VMs.
Attempting to enter custom Windows Server keys on multi-tenant Google Cloud instances results in duplicate costs because the instance is still billed automatically for the Google license-included metadata attached to the VM.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated