How does dynamic provisioning of storage in Kubernetes differ from manual provisioning?

How does dynamic provisioning of storage in Kubernetes differ from manual provisioning?

• A. Dynamic provisioning relies on pre-created PVs in the cluster
• B. Dynamic provisioning creates a new storage class for every PVC
• C. In dynamic provisioning, volumes are created automatically when a PVC is made
• D. Dynamic provisioning uses hostPath only

Answer: (C)

The key idea is that dynamic provisioning creates storage automatically when a claim is made. In manual provisioning, an administrator must first create PV resources that represent specific storage resources, and a PVC can bind only to one of these pre-existing PVs. With dynamic provisioning, a StorageClass and its provisioner handle on-demand storage creation: when a PVC requests storage, Kubernetes talks to the provisioner to create the backing storage, then creates a PV and binds it to the PVC. This eliminates the need to pre-create PVs and enables on-the-fly provisioning across various backends (cloud disks, NFS, etc.). The other statements don’t fit because provisioning isn’t tied to pre-created PVs, doesn’t require a new StorageClass for every PVC, and isn’t limited to hostPath.

The key idea is that dynamic provisioning creates storage automatically when a claim is made. In manual provisioning, an administrator must first create PV resources that represent specific storage resources, and a PVC can bind only to one of these pre-existing PVs. With dynamic provisioning, a StorageClass and its provisioner handle on-demand storage creation: when a PVC requests storage, Kubernetes talks to the provisioner to create the backing storage, then creates a PV and binds it to the PVC. This eliminates the need to pre-create PVs and enables on-the-fly provisioning across various backends (cloud disks, NFS, etc.). The other statements don’t fit because provisioning isn’t tied to pre-created PVs, doesn’t require a new StorageClass for every PVC, and isn’t limited to hostPath.