PersistentVolumeClaim (PVC) definition in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding PVC Access Modes

Which access mode allows multiple pods to read and write to the same PersistentVolume simultaneously?

A WriteOnceMany (WOM)

B ReadOnlyMany (ROX)

C ReadWriteMany (RWX)

D ReadWriteOnce (RWO)

💡 Hint

Think about which mode supports multiple writers at the same time.

ReadWriteMany (RWX) allows multiple pods to mount the volume for both reading and writing simultaneously.

💻 Command Output

intermediate

PVC Status After Creation

You create a PersistentVolumeClaim with the following YAML snippet:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: my-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 5Gi

What will be the status.phase of this PVC immediately after creation if a matching PersistentVolume is available?

A Bound

B Available

C Pending

D Lost

💡 Hint

Consider what happens when a PVC successfully binds to a PV.

When a PVC is successfully matched and bound to a PersistentVolume, its status.phase becomes 'Bound'.

❓ Configuration

advanced

Correct PVC YAML for Storage Class and Size

Which YAML snippet correctly defines a PersistentVolumeClaim requesting 10Gi storage with the storage class 'fast-storage'?

A

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: fast-pvc
spec:
  accessMode: ReadWriteOnce
  storageClass: fast-storage
  resources:
    requests:
      storage: 10GB

B

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: fast-pvc
spec:
  storageClassName: fast-storage
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

C

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: fast-pvc
spec:
  storageClassName: fast-storage
  accessModes:
    - ReadWriteMany
  resources:
    requests:
      storage: 10Gi

D

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: fast-pvc
spec:
  storageClassName: fast-storage
  accessModes:
    - ReadWriteOnce
  resources:
    limits:
      storage: 10Gi

💡 Hint

Check the correct keys for storage class, access modes, and resource requests.

Option B correctly uses 'storageClassName', 'accessModes' as a list, and 'resources.requests.storage' with '10Gi'.

❓ Troubleshoot

advanced

PVC Stuck in Pending State

You created a PVC but it remains in the 'Pending' state for a long time. Which of the following is the most likely cause?

A No PersistentVolume matches the PVC's requested size or access mode

B The PVC YAML is missing the metadata.name field

C The pod using the PVC is not running

D The PVC has already been deleted

💡 Hint

Think about what must exist for a PVC to bind successfully.

If no PersistentVolume matches the PVC's requirements, the PVC stays in 'Pending' waiting for a suitable volume.

🔀 Workflow

expert

Order of Steps to Use a PVC in a Pod

Arrange the steps in the correct order to use a PersistentVolumeClaim in a Pod.

A 2,3,1,4

B 2,1,3,4

C 1,3,2,4

D 1,2,3,4

💡 Hint

Think about what must exist before a PVC can bind and a Pod can use it.

First, a PV or dynamic provisioner must be ready. Then create the PVC to request storage. Next, define the Pod referencing the PVC. Finally, deploy the Pod to use the storage.