Volumes vs Persistent Volumes in Kubernetes - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Kubernetes Volumes vs Persistent Volumes

Which statement correctly describes the difference between a Kubernetes Volume and a Persistent Volume?

A A Volume is tied to the lifecycle of a Pod, while a Persistent Volume exists independently and can be reused by multiple Pods.

B A Volume stores data permanently on the cloud provider, while a Persistent Volume stores data only temporarily.

C A Volume is a physical disk attached to the node, while a Persistent Volume is a virtual disk inside the Pod.

D A Volume requires manual provisioning, while a Persistent Volume is always created automatically by Kubernetes.

💡 Hint

Think about the lifecycle and reusability of storage in Kubernetes Pods.

Volumes are temporary storage tied to a Pod's lifecycle. Persistent Volumes are independent storage resources that can outlive Pods and be reused.

💻 Command Output

intermediate

Output of kubectl get pv command

What is the expected output when running kubectl get pv in a cluster with one Persistent Volume named pv-data that is Available and has a capacity of 10Gi?

A

NAME      CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
pv-data   10Gi       RWX            Delete           Bound       default/myclaim   fast   5d

B

NAME      CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
pv-data   10Gi       RWO            Retain           Available           standard              5d

C

NAME      CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM   STORAGECLASS   REASON   AGE
pv-data   5Gi        RWO            Retain           Available           standard              5d

D Error from server (NotFound): persistentvolumes "pv-data" not found

💡 Hint

Check the status and capacity fields for an Available Persistent Volume.

An Available Persistent Volume shows no claim and has the status 'Available'. Capacity matches the provisioned size.

❓ Configuration

advanced

Correct Persistent Volume YAML Configuration

Which YAML snippet correctly defines a Persistent Volume with 20Gi storage, ReadWriteOnce access mode, and a Retain reclaim policy?

A

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-storage
spec:
  capacity:
    storage: 20Gi
  accessModes:
    - ReadOnlyMany
  persistentVolumeReclaimPolicy: Retain
  hostPath:
    path: /mnt/data

B

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-storage
spec:
  capacity:
    storage: 20GB
  accessModes:
    - ReadWriteMany
  persistentVolumeReclaimPolicy: Delete
  hostPath:
    path: /mnt/data

C

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-storage
spec:
  capacity:
    storage: 20Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Retain
  hostPath:
    path: /mnt/data

D

apiVersion: v1
kind: PersistentVolume
metadata:
  name: pv-storage
spec:
  capacity:
    storage: 20Gi
  accessModes:
    - ReadWriteOnce
  persistentVolumeReclaimPolicy: Delete
  hostPath:
    path: /mnt/data

💡 Hint

Check storage size units, access modes, and reclaim policy spelling.

Option C uses correct storage size unit 'Gi', access mode 'ReadWriteOnce', and reclaim policy 'Retain'.

❓ Troubleshoot

advanced

Troubleshooting Pod Volume Mount Failure

A Pod fails to start with the error MountVolume.SetUp failed for volume "data" : persistentvolumeclaim "data-pvc" not found. What is the most likely cause?

A The Kubernetes node does not have enough disk space.

B The PersistentVolume is not bound to any PersistentVolumeClaim.

C The Pod's container image is missing the volume mount path.

D The PersistentVolumeClaim named 'data-pvc' does not exist in the Pod's namespace.

💡 Hint

Focus on the error message about the PersistentVolumeClaim.

The error indicates the PersistentVolumeClaim 'data-pvc' is missing, so the Pod cannot mount the volume.

🔀 Workflow

expert

Order of Steps to Use Persistent Volumes in Kubernetes

Arrange the steps in the correct order to use a Persistent Volume in a Kubernetes Pod.

A 1,2,4,3

B 2,1,4,3

C 1,4,2,3

D 2,4,1,3

💡 Hint

Think about resource creation and binding before Pod deployment.

First create the PersistentVolume, then the PersistentVolumeClaim, verify binding, then deploy the Pod.