Question

A retail company runs a stateful microservices application on Azure Kubernetes Service (AKS) in the East US region. The application uses Azure Disk-backed persistent volumes for a self-hosted database and configuration state. Leadership requires a documented disaster recovery plan that can bring the full application—including its persistent data—back online in the West US region within an RTO of 2 hours and an RPO of 30 minutes if East US becomes unavailable. The team wants a repeatable, automated, cloud-native approach that captures both Kubernetes objects and volume data. Which approach best meets these requirements?

Accepted Answer

Deploy a second AKS cluster in West US and use Velero with scheduled backups to an Azure Blob container (with volume snapshots) that is geo-replicated, restoring both Kubernetes resources and persistent volumes during failover.

Answer

Enable AKS availability zones across three zones in East US so the cluster survives a datacenter failure without needing a second region.

Answer

Rely on Azure Site Recovery to replicate the AKS agent node VMs to West US and fail them over during a regional outage.

Answer

Store all persistent data in a locally redundant Azure Disk and manually re-create the Kubernetes manifests in a West US cluster after an outage.