Examkin

Question

Difficulty: EasyPlanning Google Kubernetes Engine (GKE) Cluster Architectures

A company is planning to deploy a lightweight internal web portal on Google Cloud. The DevOps team wants Google Cloud to manage all underlying node infrastructure, including automatic provisioning, scaling, node maintenance, and security hardening, without needing to manually define or manage node pools. Which GKE mode of operation should the team choose to meet these requirements?

  1. GKE Autopilot modeAnswer
  2. B
    GKE Standard mode with custom node pools
  3. C
    GKE Standard mode using Spot VM node pools
  4. D
    Compute Engine Managed Instance Groups (MIGs) running custom Kubernetes containers

Answer

Deploying the workload using GKE Autopilot mode fulfills the requirement because Google Cloud manages the cluster nodes, sizing, security configuration, and node scaling automatically.
GKE Autopilot mode fully automates node provisioning, cluster scaling, node maintenance, and security hardening. Users focus solely on defining workload pod specifications, making it the ideal choice when zero node-management overhead is requested.

Step-by-Step Solution

1
Identify the primary operational requirement from the scenario.
The team requires zero manual node pool configuration and complete infrastructure management by Google Cloud.
Choosing the correct GKE cluster architecture depends on evaluating operational overhead versus cluster customization control.
2
Evaluate GKE deployment modes against the operational requirement.
GKE Autopilot provisions and manages nodes automatically based on pod specifications, while GKE Standard requires manual management of node pools.
Autopilot shifts node provisioning, scaling, and maintenance responsibilities entirely to Google Cloud.

Key Concept

GKE Autopilot vs. Standard Operational Boundaries
Rate this question

Topics

Planning Google Kubernetes Engine (GKE) Cluster Architectures

More questions from this topic