Which resource references a StorageClass to provision storage for a pod, and what does the StorageClass define?

• A. Deployment references a StorageClass; StorageClass defines provisioning parameters and storage type.
• B. PersistentVolumeClaim references a StorageClass; StorageClass defines access modes.
• C. PersistentVolume references a StorageClass; StorageClass defines retention policy.
• D. Job references a StorageClass; StorageClass defines provisioning parameters.

Answer: (B)

The key idea is dynamic storage provisioning. A Pod doesn’t talk to a StorageClass directly; instead, a PersistentVolumeClaim asks for storage and can specify a StorageClass by name. When the PVC is created with that StorageClass, the cluster’s provisioner creates a matching PersistentVolume to satisfy the claim, and the Pod can then mount it via the PVC.

The StorageClass defines how to provision storage: which provisioner to use (the driver that actually creates the volume) and the provisioning parameters (such as storage type, performance characteristics, and other driver-specific options). It can also set handling details like reclaimPolicy and volumeBindingMode. Access modes are properties of the PVC and the resulting PV, not of the StorageClass itself.

So, the resource that references a StorageClass to provision storage for a pod is the PersistentVolumeClaim, and the StorageClass describes the provisioning parameters and the storage type.