Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A software development company is modernizing an application suite by moving away from deploying individual services on separate virtual machines (VMs), where operating system overhead has increased costs. The engineering team wants to adopt a container-based deployment model in Google Cloud that meets the following requirements:
Which Google Cloud compute deployment option should the company choose?
Cloud Run is a fully managed, serverless container platform based on the Knative API. It allows developers to deploy and run stateless containerized web applications, microservices, and jobs directly on Google infrastructure without provisioning or managing servers or clusters.
Although Cloud Run packages applications as containers for portability and completely removes infrastructure management overhead, it eliminates Kubernetes clusters altogether. Because Cloud Run uses the higher-level Knative API rather than exposing a Kubernetes cluster, it does not support native Kubernetes orchestration features such as Horizontal Pod Autoscaler (HPA) or Vertical Pod Autoscaler (VPA).
The engineering team wanted to deploy stateless containers on a serverless platform that scales automatically based on incoming web requests without using Kubernetes or managing clusters.
Cloud Run and GKE Autopilot both free developers from server administration, but they serve different architectural needs. Cloud Run is ideal for lightweight, stateless services that benefit from a simplified serverless model, whereas GKE Autopilot is designed for teams that specifically need Kubernetes orchestration and pod autoscaling tools.
Compute Engine is Google Cloud's core Infrastructure as a Service (IaaS) platform that provides self-managed virtual machine (VM) and bare metal instances. A Managed Instance Group (MIG) provisions a collection of identical or similarly configured VMs from an instance template, providing VM-level autoscaling, autohealing, and rolling updates.
Compute Engine with MIGs manages infrastructure at the virtual machine level rather than providing managed Kubernetes orchestration. Even if the team deploys Docker containers onto VMs using Container-Optimized OS images, orchestration and VM infrastructure remain self-managed, and running one container per VM fails to eliminate guest operating system overhead across low-utilization microservices.
The company needed full control over the operating system and kernel, had heavily utilized applications suited for dedicated VMs, and wanted to automate VM-level autoscaling and rolling replacements using instance templates.
While Compute Engine supports deploying containers on VMs and MIGs using Container-Optimized OS and docker run startup scripts, this approach still requires managing VM infrastructure. GKE is much more efficient for microservices because it packs multiple containers onto shared nodes and automates Kubernetes orchestration.
Google Kubernetes Engine (GKE) in Standard mode is a container orchestration mode where Google manages the Kubernetes control plane and node operating systems, while the customer retains configuration and management responsibility for the underlying cluster node pools.
While GKE Standard supports container portability and provides Kubernetes orchestration tools like Horizontal and Vertical Pod Autoscalers, it does not offload node management entirely to Google. In Standard mode, the engineering team must provision, configure, and manage cluster node pools rather than having Google manage the nodes and capacity adjustments automatically without manual intervention.
The organization needed granular administrative control over cluster node pools, custom node pool sizing, or specific node-level configurations while orchestrating microservices with Kubernetes.
Both Standard mode and Autopilot mode run on GKE and support HPA, VPA, and Kueue for batch orchestration. However, Autopilot mode fully abstracts away node pool management so Google handles all node capacity adjustments, whereas Standard mode requires teams to manage their own node pools.
Google Kubernetes Engine (GKE) is a managed Kubernetes platform used to deploy, scale, and orchestrate containerized applications and distributed microservices. When deployed in Autopilot mode, Google manages the entire underlying cluster infrastructure, including the Kubernetes control plane, cluster nodes, operating systems, and automatic capacity adjustments.
GKE in Autopilot mode is the optimal solution because it delivers full Kubernetes orchestration and pod-level scaling while eliminating the operational burden of managing virtual machines or node pools. Unlike Compute Engine, which requires self-managed VM administration, or GKE in Standard mode, which requires managing cluster node pools, GKE Autopilot lets teams focus exclusively on their containerized applications.
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