Your company just experienced a Google Kubernetes Engine (GKE) API outage due to a zone failure. You want to deploy a highly available GKE architecture that minimizes service interruption to users in

The correct answer is B. Deploy Regional clusters. A Regional GKE cluster distributes both the control plane (API server, etcd) and worker nodes across multiple zones within a region. If one zone fails, the API server remains available because replicas exist in the other zones - directly solving the described outage scenario. A Z

Designing highly available and reliable cloud-native applications

Question

Your company just experienced a Google Kubernetes Engine (GKE) API outage due to a zone failure. You want to deploy a highly available GKE architecture that minimizes service interruption to users in the event of a future zone failure. What should you do?

Options

ADeploy Zonal clusters
BDeploy Regional clusters
CDeploy Multi-Zone clusters
DDeploy GKE on-premises clusters

How the community answered

(41 responses)

A
2% (1)
B
78% (32)
C
7% (3)
D
12% (5)

Explanation

A Regional GKE cluster distributes both the control plane (API server, etcd) and worker nodes across multiple zones within a region. If one zone fails, the API server remains available because replicas exist in the other zones - directly solving the described outage scenario. A Zonal cluster (A) places the control plane in a single zone, making it vulnerable to exactly this failure. A Multi-zone cluster (C) is an older GKE concept where nodes span multiple zones but the control plane still lives in a single zone - it improves node availability but does not protect the API server. GKE on-premises (D) is unrelated to Google Cloud zone failure resilience.

Topics

#GKE#High Availability#Fault Tolerance#Regional Clusters

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice