Microsoft Certified: Azure Developer Associate (AZ-204)Develop Azure compute solutionsHard
A company is deploying a new containerized application to Azure Kubernetes Service (AKS). The application requires persistent storage that can be shared across multiple pods and dynamically provisioned as needed. The storage solution must be highly available and resilient to node failures. Which type of Azure storage should be used for this requirement?
- AAzure Table Storage
- BAzure Files
- CAzure Blob Storage
- DAzure Queue Storage
Show answer & explanationAnswer & explanation
Correct answer: B. Azure Files
Azure Files provides fully managed file shares in the cloud that are accessible via the Server Message Block (SMB) protocol or Network File System (NFS) protocol. It can be mounted by multiple pods in AKS, supports dynamic provisioning via Persistent Volume Claims, and is highly available and resilient, making it ideal for shared persistent storage in Kubernetes.
Why the other options are wrong
- A. Table Storage is for NoSQL key-value data, not for file system storage.
- C. Blob Storage is for object storage (unstructured data like images, videos), not designed for file system mounting by multiple pods simultaneously.
- D. Queue Storage is for message queuing, not for persistent file storage.
Azure Files for AKS
Azure Files provides fully managed file shares that can be mounted by Azure Kubernetes Service (AKS) pods as shared persistent storage using the Server Message Block (SMB) or Network File System (NFS) protocols.
- Supports ReadWriteMany access mode (multiple pods can write simultaneously)
- Integrates with Kubernetes Persistent Volume Claims (PVCs)
- Highly available and durable
- Can be dynamically provisioned
Memory trick: Files for AKS is like a shared drive, Disks are for single pods, Blob is for objects, Queues for messages alive.