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 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:
Which Compute Engine deployment strategy should you recommend?
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.
Kubernetes taints and tolerations are scheduling mechanisms used in Google Kubernetes Engine (GKE) to prevent pods from being scheduled onto inappropriate nodes and to dedicate specific node pools to particular containerized workloads.
The database application was already containerized and the primary goal was logical workload segregation across Kubernetes node pools rather than physical hardware-bound license compliance.
Standard multi-tenant Compute Engine instances run virtual machines on shared physical hardware alongside workloads from other Google Cloud customers, separated logically by the hypervisor.
The software vendor supported licensing purely based on virtual CPUs (vCPUs) with unrestricted license mobility across shared multi-tenant cloud environments.
License-included Compute Engine instances are pre-configured virtual machine images where the operating system and database software licenses (such as Microsoft Windows Server or SQL Server) are billed on a pay-as-you-go operational expense model by Google Cloud per second or per hour of usage.
The organization had no existing software licenses, needed short-term transient workloads, or wanted to transition entirely from capital license expenditures to operational licensing models without managing software renewals.
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