Certified Kubernetes Application Developer (CKAD) Practice Test

What is the key difference between static and dynamic persistent volume provisioning?

1. Static volumes require user intervention to create before binding

2. Dynamic volumes are only used for temporary storage

3. Static volumes can be resized after creation

4. Dynamic volumes do not require storage classes

The correct answer is: Static volumes require user intervention to create before binding

The key difference between static and dynamic persistent volume provisioning lies in how the persistent volumes are created and managed. Static provisioning requires that an administrator pre-create persistent volumes in the cluster before they can be bound to storage claims. This means that for each volume needed, a specific action is performed by the user to ensure it is available for allocation. In contrast, dynamic provisioning allows volumes to be created on-demand based on the needs of the applications when a persistent volume claim (PVC) is made. The dynamic provisioning process uses a storage class to automate the creation of volumes, which means that users can request storage without the prior knowledge of how many volumes are needed or their specifications. This distinction underscores the operational difference where static volumes need to be proactively managed, while dynamic volumes streamline this process by automatically creating them according to defined policies and user requests. The options regarding temporary storage and resizing, as well as the relationship of dynamic volumes with storage classes, address other aspects of persistent volumes but do not capture the foundational difference between static and dynamic provisioning.