Examkin

Soru

Zorluk: ZorPlanning Google Kubernetes Engine (GKE) Cluster Architectures

An e-commerce enterprise is architecting a Google Kubernetes Engine (GKE) environment to process core transactional events and inventory updates. The system must meet three strict architectural requirements:
1. High availability: The control plane and worker workloads must withstand a complete single-zone outage without service disruption.
2. Zero node management overhead: The infrastructure team must not manage, patch, or configure underlying Compute Engine virtual machine instances or node pools.
3. Automatic scaling: Compute resources must dynamically scale down when demand drops to eliminate unnecessary costs.

Which GKE cluster architecture configuration best satisfies all these requirements?

  1. Deploy a Regional GKE Autopilot cluster distributed across multiple availability zones.Cevap
  2. B
    Deploy a Zonal GKE Standard cluster and configure a single node pool spanning three zones.
  3. C
    Deploy a Zonal GKE Standard cluster using Spot VMs across all node pools to automate node lifecycle management and ensure zero downtime.
  4. D
    Deploy a Regional GKE Standard cluster and rely on the Horizontal Pod Autoscaler (HPA) to automatically provision and patch worker VM instances.

Cevap

Deploying a Regional GKE Autopilot cluster distributed across multiple availability zones satisfies high availability, zero node management overhead, and automated resource scaling.
A Regional GKE Autopilot cluster provides a multi-zonal control plane for fault tolerance against zonal outages, while fully managing node lifecycle, OS patching, and automatic infrastructure scaling to eliminate operational overhead.

Adım Adım Çözüm

1
Analyze high availability requirements
A regional cluster control plane is replicated across multiple zones, preventing control plane downtime during a single-zone failure, unlike a zonal cluster.
Zonal clusters host the master control plane in a single zone, creating a single point of failure.
2
Evaluate operational management boundaries
GKE Autopilot manages the underlying node infrastructure, OS patching, and node provisioning automatically.
GKE Standard leaves node maintenance, OS upgrades, and node pool configuration to the administrator.
3
Verify autoscaling capabilities
Autopilot dynamically provisions and scales resource capacity based on pod resource requests without manual node pool sizing.
Workload resource requirements are met seamlessly while optimizing operational expenditures.

Anahtar Kavram

GKE Autopilot vs. Standard Operational Boundaries and Regional vs. Zonal High Availability Planning
Bu soruyu puanla

Konular

Planning Google Kubernetes Engine (GKE) Cluster Architectures

Bu konudan daha fazla soru