Which object represents a user's claim to storage resources defined by a PersistentVolume?

Which object represents a user's claim to storage resources defined by a PersistentVolume?

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

Answer: (C)

In Kubernetes, storage is requested by users through a PersistentVolumeClaim. The claim specifies what you need—size, access mode, and optionally a storage class—and acts as the user’s binding to the underlying storage defined by a PersistentVolume. When a PVC is created, the control plane finds a matching PV and binds to it, enabling you to mount that storage in your Pod via a volume that references the PVC. This decouples the storage provider from the Pod lifecycle, so the storage resource persists beyond individual Pod runs. A Pod is a runtime unit that runs containers; a Deployment manages Pods; a ConfigMap stores configuration data and does not represent a storage claim.

In Kubernetes, storage is requested by users through a PersistentVolumeClaim. The claim specifies what you need—size, access mode, and optionally a storage class—and acts as the user’s binding to the underlying storage defined by a PersistentVolume. When a PVC is created, the control plane finds a matching PV and binds to it, enabling you to mount that storage in your Pod via a volume that references the PVC. This decouples the storage provider from the Pod lifecycle, so the storage resource persists beyond individual Pod runs. A Pod is a runtime unit that runs containers; a Deployment manages Pods; a ConfigMap stores configuration data and does not represent a storage claim.