Examkin

Question

Difficulty: MediumPlanning Google Kubernetes Engine (GKE) Cluster Architectures

An enterprise SaaS company is planning the architecture for a new containerized web application on Google Kubernetes Engine (GKE). The application consists of stateless microservices that scale dynamically based on HTTP traffic. The infrastructure team wants to eliminate manual node provisioning, OS patching, and capacity planning while ensuring Google manages the cluster infrastructure health and node lifecycle entirely. Additionally, organizational policy forbids running pods with privileged host access. Which GKE mode should the cloud engineer choose to meet these requirements?

  1. Provision a GKE Autopilot cluster, allowing Google Cloud to fully manage the underlying node infrastructure and enforce built-in security baselines.Answer
  2. B
    Provision a GKE Standard cluster with node auto-provisioning enabled, because Autopilot requires operators to manually install node operating system security patches.
  3. C
    Provision a GKE Standard cluster using Spot VM node pools exclusively for the control plane nodes to eliminate control plane management costs.
  4. D
    Provision a GKE Standard cluster with a single zonal node pool and disable the Cluster Autoscaler to eliminate cluster management overhead.

Answer

Provision a GKE Autopilot cluster, allowing Google Cloud to fully manage the underlying node infrastructure and enforce built-in security baselines.
GKE Autopilot is designed to provide a fully managed environment where Google handles the cluster infrastructure, including node provisioning, auto-scaling, auto-repair, and OS patching. It also enforces security best practices by blocking privileged pod execution by default, making it the ideal choice for stateless microservices with zero node administration overhead.

Step-by-Step Solution

1
Analyze the operational and management requirements specified in the scenario.
The requirements demand zero node management overhead (automated provisioning, health, and OS patching) for stateless microservices alongside strict pod security constraints.
Understanding the operational boundary helps evaluate the appropriate GKE cluster deployment mode.
2
Compare GKE Autopilot and GKE Standard operational models.
GKE Autopilot completely manages node provisioning, scaling, security hardening, and OS updates, while GKE Standard requires administration of node pools, underlying Compute Engine instances, and node OS upgrades.
Matching workload needs to GKE mode features ensures compliance with architectural goals.
3
Select the GKE mode that fulfills all constraints.
GKE Autopilot provides a hands-off cluster architecture ideal for stateless microservices while enforcing baseline security controls.
Autopilot satisfies the zero node-management overhead mandate while maintaining security compliance.

Key Concept

GKE Autopilot vs. Standard Cluster Architecture Planning
Rate this question

Topics

Planning Google Kubernetes Engine (GKE) Cluster Architectures

More questions from this topic