Kubernetes Container Orchestration Storage Solutions 2

Question 1

Which Kubernetes object allows a pod to request storage without knowing the underlying storage implementation?

Accepted Answer

PersistentVolumeClaim

Answer

A PersistentVolumeClaim (PVC) abstracts storage details so pods can request storage without awareness of the underlying provider.

Question 2

What happens to a PersistentVolume with ReclaimPolicy 'Retain' after its PVC is deleted?

Accepted Answer

The PV is released but data is preserved and must be manually reclaimed

Answer

With the Retain policy, the PV moves to Released state and retains its data, requiring manual administrator intervention to reclaim.

Question 3

Which access mode allows a PersistentVolume to be mounted as read-write by many nodes simultaneously?

Accepted Answer

ReadWriteMany

Answer

ReadWriteMany (RWX) permits the volume to be mounted read-write by multiple nodes at the same time.

Question 4

In a StorageClass definition, what field specifies how volumes are provisioned when a PVC is created?

Accepted Answer

provisioner

Answer

The 'provisioner' field in a StorageClass identifies the plugin or driver (e.g., kubernetes.io/aws-ebs) responsible for creating volumes.

Question 5

What does the 'volumeBindingMode: WaitForFirstConsumer' setting on a StorageClass accomplish?

Accepted Answer

Delays PV provisioning until a pod using the PVC is scheduled

Answer

WaitForFirstConsumer defers volume binding and provisioning until a pod that uses the PVC is actually scheduled, enabling topology-aware placement.

Kubernetes Container Orchestration Practice Test