Which Kubernetes resource should you use to provide persistent data storage for an application?

Which Kubernetes resource should you use to provide persistent data storage for an application?

• A. ConfigMap
• B. Secret
• C. Persistent Volume
• D. Service

Answer: (C)

Persistent storage in Kubernetes is provided by volumes that outlive individual pods. The resource that represents the actual storage in the cluster is the PersistentVolume. It defines the storage capacity, access modes, and the underlying storage source (such as a disk, NFS, or a cloud disk). The application doesn’t mount a PV directly; instead, it uses a PersistentVolumeClaim, which requests storage and is bound to a suitable PV. This separation allows flexible, persistent storage management, including dynamic provisioning via StorageClass. ConfigMap and Secret are for configuration data and sensitive data, not for persistent application data. A Service is for exposing and routing traffic to pods, not for storage.

Persistent storage in Kubernetes is provided by volumes that outlive individual pods. The resource that represents the actual storage in the cluster is the PersistentVolume. It defines the storage capacity, access modes, and the underlying storage source (such as a disk, NFS, or a cloud disk). The application doesn’t mount a PV directly; instead, it uses a PersistentVolumeClaim, which requests storage and is bound to a suitable PV. This separation allows flexible, persistent storage management, including dynamic provisioning via StorageClass.

ConfigMap and Secret are for configuration data and sensitive data, not for persistent application data. A Service is for exposing and routing traffic to pods, not for storage.