Examkin

Question

Difficulty: EasyPlanning Google Kubernetes Engine (GKE) Cluster Architectures

A startup is planning to deploy a containerized application on Google Kubernetes Engine (GKE). The DevOps team wants a fully managed solution where Google automatically provisions, configures, and scales the underlying node infrastructure based on pod specifications, eliminating the need to manage node pools manually. Which GKE cluster operational mode should the team select?

  1. GKE Autopilot modeAnswer
  2. B
    GKE Standard mode with custom node pools
  3. C
    GKE Standard mode using Spot VMs for the control plane
  4. D
    GKE Standard mode managed exclusively by Horizontal Pod Autoscaler

Answer

GKE Autopilot mode is the correct choice because Google manages node provisioning, scaling, and cluster maintenance, eliminating node-level management overhead.
GKE Autopilot mode provides a fully managed cluster architecture where Google handles node provisioning, auto-scaling, security patching, and node configuration. This satisfies the requirement of eliminating manual node management overhead.

Step-by-Step Solution

1
Analyze the operational requirements specified in the scenario.
The team requires zero node management overhead and automated node lifecycle management by Google.
Identifying management constraints determines whether Autopilot or Standard mode is appropriate.
2
Compare GKE cluster operational modes against the requirement.
GKE Autopilot automatically manages node provisioning, hardware configuration, and scaling based on pod requests.
GKE Autopilot shifts node management responsibilities completely to Google.

Key Concept

GKE Autopilot vs. Standard Operational Boundaries
Estimated Time:1m 0s
Rate this question

Topics

Planning Google Kubernetes Engine (GKE) Cluster Architectures

More questions from this topic