Your application requires a persistent volume. How should you configure it?

Correct answer: Create a PersistentVolume and PersistentVolumeClaim

Option D is correct because Kubernetes separates storage provisioning (PersistentVolume) from consumption (PersistentVolumeClaim), giving applications a stable, durable storage resource that survives Pod restarts and rescheduling. Option A is wrong because ephemeral volumes, such as emptyDir, exist only for the lifetime of the Pod and lose all data when the Pod terminates. Option B is inadvisable for production workloads because hostPath volumes tie the Pod to a specific node, undermining portability and creating data-loss risk if the Pod is rescheduled. Option C describes the same anti-pattern as hostPath and is never a supported Kubernetes abstraction for persistent storage.