Hotspot Question You need to create deployment files for an Azure Kubernetes Service (AKS) cluster. The deployments must meet the provisioning storage requirements shown in the following table. Which

Question

Exhibits

Answer Area

• Deployment 1PersistentVolumeClaim
  PersistentVolumeClaimSecretConfigMapStorageClassEmptyDir
• Deployment 2PersistentVolumeClaim
  PersistentVolumeClaimSecretConfigMapStorageClassEmptyDir
• Deployment 3Secret
  PersistentVolumeClaimSecretConfigMapStorageClassEmptyDir

Explanation

This question tests knowledge of Kubernetes storage resource types in AKS, specifically when to use PersistentVolume (PV), PersistentVolumeClaim (PVC), and StorageClass based on provisioning requirements like static vs. dynamic provisioning and shared vs. dedicated storage.

Approach. For static provisioning (pre-provisioned Azure Disk or Azure Files), you use a PersistentVolume (PV) to represent the existing storage resource and a PersistentVolumeClaim (PVC) to request/bind to it. For dynamic provisioning where storage is automatically created on demand, you use a StorageClass which defines the provisioner (e.g., azure-disk, azure-file) and parameters, allowing Kubernetes to automatically create the underlying storage when a PVC references that StorageClass. Azure Files-backed storage uses StorageClass with the 'kubernetes.io/azure-file' provisioner when dynamic shared (ReadWriteMany) access is needed, while Azure Disk uses StorageClass with 'kubernetes.io/azure-disk' for dynamic exclusive (ReadWriteOnce) access.

Concept tested. AKS Kubernetes storage resource types: PersistentVolume (PV) for static provisioning of pre-existing storage, PersistentVolumeClaim (PVC) for requesting storage, and StorageClass for dynamic provisioning - understanding which to use based on whether storage is pre-provisioned or dynamically created, and whether it uses Azure Disk or Azure Files.

Reference. https://learn.microsoft.com/en-us/azure/aks/concepts-storage

No community discussion yet for this question.