nerdexam
Amazon

SAP-C02 · Question #670

A company is preparing to deploy an Amazon Elastic Kubernetes Service (Amazon EKS) cluster for a workload. The company expects the cluster to support an unpredictable number of stateless pods. Many…

The correct answer is D. Configure the workload to use topology spread constraints that are based on Availability Zone. The goal is to maximize node resilience for an EKS cluster with an unpredictable, rapidly scaling number of stateless pods.

Submitted by noor.lb· Mar 6, 2026Design for New Solutions

Question

A company is preparing to deploy an Amazon Elastic Kubernetes Service (Amazon EKS) cluster for a workload. The company expects the cluster to support an unpredictable number of stateless pods. Many of the pods will be created during a short time period as the workload automatically scales the number of replicas that the workload uses. Which solution will MAXIMIZE node resilience?

Options

  • AUse a separate launch template to deploy the EKS control plane into a second cluster that is
  • BUpdate the workload node groups. Use a smaller number of node groups and larger instances in
  • CConfigure the Kubernetes Cluster Autoscaler to ensure that the compute capacity of the workload
  • DConfigure the workload to use topology spread constraints that are based on Availability Zone.

How the community answered

(45 responses)
  • A
    27% (12)
  • B
    11% (5)
  • C
    7% (3)
  • D
    56% (25)

Why each option

The goal is to maximize node resilience for an EKS cluster with an unpredictable, rapidly scaling number of stateless pods.

AUse a separate launch template to deploy the EKS control plane into a second cluster that is

Deploying the EKS control plane to a second cluster is not related to maximizing node resilience for the workload's pods; EKS already manages control plane redundancy across AZs.

BUpdate the workload node groups. Use a smaller number of node groups and larger instances in
CConfigure the Kubernetes Cluster Autoscaler to ensure that the compute capacity of the workload
DConfigure the workload to use topology spread constraints that are based on Availability Zone.Correct

Configuring the workload to use topology spread constraints based on Availability Zone ensures that pods are evenly distributed across multiple AZs. This strategy prevents a single AZ failure from significantly impacting the entire workload, thus maximizing node resilience and ensuring high availability during rapid scaling events.

Concept tested: Kubernetes topology spread constraints for high availability

Source: https://kubernetes.io/docs/concepts/workloads/pods/pod-topology-spread-constraints/

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full SAP-C02 Practice