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 hundreds of legacy on-premises Windows Server and Red Hat Enterprise Linux (RHEL) workloads to Google Compute Engine. Software licensing fees make up a significant portion of the total operating budget because OS vendor licenses are billed on a per-vCPU basis.
During pre-migration discovery in Migration Center, performance data reveals that the on-premises servers are substantially over-provisioned. Additionally, the corporate compliance team requires automated, continuous auditing of deployed machine shapes and operating system licensing models post-migration to avoid contractual penalties.
Which strategy should the cloud architect implement to optimize licensing costs and ensure ongoing license compliance?
This proposal refactors the enterprise's legacy Windows and RHEL operating system environments into containerized applications running on Google Kubernetes Engine (GKE), enclosed within a VPC Service Controls perimeter.
The scenario focused on modernizing cloud-native microservices and mitigating insider data exfiltration threats across managed storage buckets.
While GKE provides flexible container orchestration, standard enterprise infrastructure migrations typically leverage Migration Center rightsizing and Compute Engine VM licensing models first.
Performance-based rightsizing combined with simultaneous multithreading (SMT) tuning in Migration Center optimizes compute resource allocation and direct per-vCPU operating system licensing fees. Combining this optimization with Cloud Asset Inventory and Cloud Audit Logs creates a continuous auditing mechanism that tracks resource configuration changes and licensing compliance across Google Cloud environments.
This approach directly tackles the core driver of enterprise licensing costs—unnecessary vCPU allocations—while using native cloud auditing mechanisms to maintain continuous governance and audit readiness without adding manual operational overhead.
A 1:1 hardware core mapping performs a direct lift-and-shift of on-premises CPU allocations onto Google Cloud Sole-Tenant Nodes, maintaining existing core allocations without rightsizing adjustments, coupled with periodic manual administrative scripts for audit validation.
The workloads had rigid contractual requirements prohibiting any virtualization or performance rightsizing, and if real-time compliance tracking was not required.
Rightsizing before migrating to sole-tenant environments is essential to ensure that the minimum number of physical nodes are licensed.
This option involves purchasing Committed Use Discounts (CUDs) based directly on current on-premises vCPU numbers and using Google Cloud Armor to maintain license compliance.
The primary goal was to secure predictable pricing on steady-state workloads that were already rightsized, and protect public endpoints against layer 7 application attacks.
Commitments should always be purchased after workloads are rightsized and stabilized in the cloud environment.
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 Validated