Question

A company runs a stateless microservices application on Azure Kubernetes Service (AKS) in a single region. Business requirements now mandate that the application remain available even if an entire Azure datacenter (availability zone) fails, with no manual intervention. The solution must minimize administrative overhead and avoid cross-region complexity. Which design should you recommend?

Accepted Answer

Deploy a single AKS cluster with node pools spread across multiple availability zones and configure pod anti-affinity across zones.

Answer

Deploy two AKS clusters in two separate Azure regions and use Azure Front Door to distribute traffic between them.

Answer

Deploy a single AKS cluster in one availability zone and configure Azure Backup to protect the cluster nodes.

Answer

Deploy a single-zone AKS cluster and enable the cluster autoscaler to add nodes when a zone becomes unavailable.