What is the primary purpose of a Persistent Volume (PV) in Kubernetes?

What is the primary purpose of a Persistent Volume (PV) in Kubernetes?

• A. To store data that persists beyond the lifecycle of a pod
• B. To attach and manage container images
• C. To schedule pods onto nodes
• D. To define network policies

Answer: (A)

A Persistent Volume provides durable storage that lives beyond the life of any single Pod. In Kubernetes, a PV represents a piece of storage in the cluster, and it exists independently of Pods. A Pod can request that storage by using a PersistentVolumeClaim, and once bound, can read and write data to that storage even if the Pod is recreated, rescheduled, or deleted. This decouples storage management from the Pod lifecycle and supports various backends (local disks, network file systems, cloud disks, etc.), making stateful applications reliable across restarts and migrations. The other options describe different aspects of the cluster—managing container images, scheduling pods onto nodes, and defining network policies—which are not about persistent storage.

A Persistent Volume provides durable storage that lives beyond the life of any single Pod. In Kubernetes, a PV represents a piece of storage in the cluster, and it exists independently of Pods. A Pod can request that storage by using a PersistentVolumeClaim, and once bound, can read and write data to that storage even if the Pod is recreated, rescheduled, or deleted. This decouples storage management from the Pod lifecycle and supports various backends (local disks, network file systems, cloud disks, etc.), making stateful applications reliable across restarts and migrations. The other options describe different aspects of the cluster—managing container images, scheduling pods onto nodes, and defining network policies—which are not about persistent storage.