Kubernetes Container Orchestration Storage Solutions 5

Question 1

What Kubernetes feature allows storage capacity information to be published so the scheduler can make volume-aware placement decisions?

Accepted Answer

CSIStorageCapacity objects

Answer

CSIStorageCapacity objects, created by CSI drivers, expose available capacity per topology segment so the scheduler avoids placing pods where storage would be insufficient.

Question 2

Which kubectl command shows the events associated with a PersistentVolumeClaim to help diagnose binding issues?

Accepted Answer

kubectl describe pvc <name>

Answer

kubectl describe pvc shows the full PVC spec, status, and the Events section which lists binding attempts, provisioner errors, and other diagnostic messages.

Question 3

What is the effect of setting 'ReadWriteOncePod' as the access mode for a PersistentVolumeClaim?

Accepted Answer

The volume can be mounted by one pod at a time across the entire cluster

Answer

ReadWriteOncePod (RWOP), introduced in Kubernetes 1.22, ensures the volume is mounted by exactly one pod across the whole cluster, stricter than ReadWriteOnce.

Question 4

In the context of Kubernetes storage, what does 'dynamic provisioning' mean?

Accepted Answer

A StorageClass provisioner automatically creates a PV when a matching PVC is submitted

Answer

Dynamic provisioning means a provisioner plugin (in-tree or CSI) automatically creates a PersistentVolume to satisfy a PVC without manual administrator intervention.

Question 5

What must be true for a PersistentVolume to bind to a PersistentVolumeClaim?

Accepted Answer

The PV capacity, access mode, and StorageClass must all satisfy the PVC's request

Answer

Kubernetes binds a PV to a PVC only when the PV's capacity is at least as large as requested, the access modes overlap, and the StorageClass names match.

Kubernetes Container Orchestration Practice Test

Kubernetes Container Orchestration Practice Test

Kubernetes Container Orchestration Storage Solutions 5