PROFESSIONAL-CLOUD-DEVELOPER · Question #220
You are deploying a microservices application to Google Kubernetes Engine (GKE) that will broadcast livestreams. You expect unpredictable traffic patterns and large variations in the number of concurr
The correct answer is A. Distribute your workload evenly using a multi-zonal node pool. C. Use cluster autoscaler to resize the number of nodes in the node pool, and use a Horizontal Pod. A multi-zonal node pool (A) distributes nodes across multiple zones in a region, so a hardware failure in one zone does not take down the entire workload - Kubernetes reschedules pods to healthy zones automatically. The Cluster Autoscaler paired with a Horizontal Pod Autoscaler (
Question
You are deploying a microservices application to Google Kubernetes Engine (GKE) that will broadcast livestreams. You expect unpredictable traffic patterns and large variations in the number of concurrent users. Your application must meet the following requirements:
- Scales automatically during popular events and maintains high
availability
- Is resilient in the event of hardware failures
How should you configure the deployment parameters? (Choose two.)
Options
- ADistribute your workload evenly using a multi-zonal node pool.
- BDistribute your workload evenly using multiple zonal node pools.
- CUse cluster autoscaler to resize the number of nodes in the node pool, and use a Horizontal Pod
- DCreate a managed instance group for Compute Engine with the cluster nodes. Configure
- ECreate alerting policies in Cloud Monitoring based on GKE CPU and memory utilization. Ask an
How the community answered
(51 responses)- A76% (39)
- B12% (6)
- D8% (4)
- E4% (2)
Explanation
A multi-zonal node pool (A) distributes nodes across multiple zones in a region, so a hardware failure in one zone does not take down the entire workload - Kubernetes reschedules pods to healthy zones automatically. The Cluster Autoscaler paired with a Horizontal Pod Autoscaler (C) handles the two dimensions of scaling: the HPA adds/removes pods based on CPU/memory demand, and the Cluster Autoscaler adds/removes nodes when pods cannot be scheduled. Together these satisfy both auto-scaling and resilience. Multiple zonal node pools (B) adds operational complexity without the same built-in HA benefit as a single multi-zonal pool. Managed instance groups (D) are a Compute Engine concept and do not apply to GKE node management. Alerting policies (E) notify humans but do not trigger automated scaling.
Topics
Community Discussion
No community discussion yet for this question.