You need persistent shared storage for an AKS Deployment named reports that runs 6 replicas across multiple nodes. Each replica must be able to read and write the same files concurrently. Data must persist across pod restarts and be backed by an Azure-managed service. What should you configure?

Azure Files (file.csi.azure.com) is the correct choice because it supports the ReadWriteMany access mode, which allows multiple pods (replicas) to concurrently read and write to the same persistent volume. This directly addresses the requirement for 6 replicas across multiple nodes to access the same files. Configuring a StorageClass and a PersistentVolumeClaim (PVC) with ReadWriteMany ensures the storage is provisioned and accessible as needed. Azure Files is a managed service, fulfilling that requirement. Azure Disks (disk.csi.azure.com) primarily supports ReadWriteOnce, meaning only one pod can mount it at a time, which doesn't meet the concurrent access requirement. A hostPath volume is not suitable for multi-node deployments as it binds storage to a specific node, and data would not be shared or persistent across node failures or pod rescheduling. An emptyDir volume provides ephemeral storage that is deleted when the pod restarts, failing the persistence requirement.