Question #934
A company is deploying an Amazon EKS cluster for a stateless web application that experiences sudden traffic surges, requiring rapid scaling of pod replicas. The company wants to ensure maximum node resilience. Which solution should they implement?
Deploy the EKS control plane across multiple Availability Zones using a dedicated node group.
Configure the Kubernetes Horizontal Pod Autoscaler to scale pods based on CPU utilization.
Use larger instance types in fewer node groups to consolidate resources.
Apply topology spread constraints to distribute pods across Availability Zones.
Explanation
Answer D is correct because topology spread constraints enforce Kubernetes to distribute pods evenly across AZs, minimizing the risk of downtime if an AZ fails. This directly addresses the requirement for maximum node resilience.
Option A is incorrect because the EKS control plane is already highly available and spans multiple AZs by default; dedicated node groups are unrelated to worker node resilience. Option B (Horizontal Pod Autoscaler) handles pod scaling but does not ensure AZ distribution. Option C (larger instances in fewer node groups) reduces AZ diversity, increasing fragility. The key takeaway: Use topology spread constraints with multi-AZ node groups to balance scaling and resilience.
Answer
The correct answer is: D