An enterprise plans to migrate legacy Microsoft Windows Server and SQL Server enterprise databases from an on-premises data center to Google Cloud. The existing software licenses are licensed per physical core and per physical socket under an enterprise agreement that supports Bring Your Own License (BYOL). The migration must satisfy the following requirements: Comply with vendor software licensing rules requiring physical hardware isolation and physical core visibility for audit purposes Reuse existing on-premises software licenses to avoid purchasing new cloud licenses Ensure high availability during underlying infrastructure maintenance without manual workload rescheduling Minimize capital expenditure and unnecessary infrastructure operational costs Which Compute Engine deployment strategy should you recommend?

Deploy the virtual machines on Compute Engine sole-tenant nodes configured with node affinity labels and a default host maintenance policy.: ### What Sole-Tenant Nodes Are **Compute Engine sole-tenant nodes** provide dedicated physical Compute Engine servers allocated exclusively for use by a single customer project. They give organizations visibility into the underlying physical hardware, including physical sockets, cores, and server hardware characteristics. ### How It Meets The Requirements - **Physical Hardware Isolation and Licensing Compliance**: Vendor licenses that are tied to **physical processor sockets or physical cores** require strict isolation and consistent hardware tracking. Sole-tenant nodes ensure that no other tenant shares the physical hardware, allowing organizations to license the physical host under **Bring Your Own License (BYOL)** terms and satisfy compliance audits. - **Reuse Existing Licenses (BYOL)**: Organizations avoid the capital and operational expense of repurchasing pay-as-you-go software licenses by bringing existing perpetual licenses directly to dedicated hardware in the cloud. - **High Availability and Maintenance**: With the default **host maintenance policy**, Compute Engine live-migrates sole-tenant workloads to another dedicated node within the same node group during host maintenance events, maintaining uptime without administrative intervention. - **Cost Optimization**: Consolidating multiple VMs onto dedicated sole-tenant nodes maximizes core density and minimizes total hardware and licensing costs. ### Key Advantages - **Hardware Visibility**: Provides full access to physical core and socket metrics required for vendor compliance reporting. - **Affinity and Anti-Affinity Labels**: Allows granular control over how virtual machines are scheduled across dedicated physical hosts. - **Live Migration Support**: Supports uninterrupted maintenance through automated live migration within dedicated node groups. - **Committed Use Discounts**: Compatible with committed use discounts (CUDs) to further optimize baseline infrastructure expenses.

StudyCerts

Byol Sole Tenant Nodes Licensing Feasibility | 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! | StudyCerts

Professional Cloud Architect

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!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Byol Sole Tenant Nodes Licensing Feasibility

Section: Determining software license implications and financial impact

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.

An enterprise plans to migrate legacy Microsoft Windows Server and SQL Server enterprise databases from an on-premises data center to Google Cloud. The existing software licenses are licensed per physical core and per physical socket under an enterprise agreement that supports Bring Your Own License (BYOL).

The migration must satisfy the following requirements:

Comply with vendor software licensing rules requiring physical hardware isolation and physical core visibility for audit purposes
Reuse existing on-premises software licenses to avoid purchasing new cloud licenses
Ensure high availability during underlying infrastructure maintenance without manual workload rescheduling
Minimize capital expenditure and unnecessary infrastructure operational costs

Which Compute Engine deployment strategy should you recommend?

Deploy the virtual machines on standard multi-tenant Compute Engine instances using custom machine types to match on-premises vCPU counts.

Deploy the virtual machines on Compute Engine sole-tenant nodes configured with node affinity labels and a default host maintenance policy.

Provision new license-included Compute Engine instances and retire existing on-premises software licenses upon migration.

Deploy the workloads onto a Google Kubernetes Engine (GKE) cluster utilizing node taints and tolerations to isolate workloads to dedicated node pools.

Professional Cloud Architect

Byol Sole Tenant Nodes Licensing Feasibility

Related questions