Which Kubernetes object is used to request storage from a pool of PersistentVolumes?

Which Kubernetes object is used to request storage from a pool of PersistentVolumes?

• A. PersistentVolume
• B. Pod
• C. ConfigMap
• D. PersistentVolumeClaim

Answer: (D)

PersistentVolumeClaim is the request for storage. In Kubernetes, a PersistentVolume represents the actual storage resource, either statically created by an administrator or created dynamically via a StorageClass. A PersistentVolumeClaim describes what you need (size, access mode, and optionally a storage class) and the control plane binds that claim to a suitable PV. Once bound, a pod can mount the storage by referencing the claim in its volume configuration. The other options don’t fit this role: a PersistentVolume is the actual storage resource, a Pod uses volumes but does not request storage directly, and a ConfigMap stores configuration data rather than persistent block or file storage. Dynamic provisioning can create a PV on demand when a PVC is created, further illustrating why the claim is the correct construct for requesting storage.

PersistentVolumeClaim is the request for storage. In Kubernetes, a PersistentVolume represents the actual storage resource, either statically created by an administrator or created dynamically via a StorageClass. A PersistentVolumeClaim describes what you need (size, access mode, and optionally a storage class) and the control plane binds that claim to a suitable PV. Once bound, a pod can mount the storage by referencing the claim in its volume configuration. The other options don’t fit this role: a PersistentVolume is the actual storage resource, a Pod uses volumes but does not request storage directly, and a ConfigMap stores configuration data rather than persistent block or file storage. Dynamic provisioning can create a PV on demand when a PVC is created, further illustrating why the claim is the correct construct for requesting storage.