[Solved] Consider this PersistentVolumeClaim YAML:apiVersion: v1 kind: PersistentVolumeClaim metadata: name: example-pvc spec: accessModes: - ReadWriteOnce resources: requests: storage:... | Kubernetes

Kubernetes - Persistent Storage

Consider this PersistentVolumeClaim YAML:

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

What will Kubernetes do if no PersistentVolume matches this claim?

AThe pod using this PVC will start without mounting any volume

BKubernetes will automatically create a new PersistentVolume

CThe PVC will remain in Pending state until a matching PV is available

DThe PVC will be deleted automatically after a timeout

Step-by-Step Solution

Solution:

Step 1: PVC binding process
A PersistentVolumeClaim waits for a PersistentVolume that satisfies its requirements.
Step 2: Behavior when no PV matches
If no suitable PersistentVolume exists, the PVC stays in Pending state until one becomes available.
Final Answer:
The PVC will remain in Pending state until a matching PV is available -> Option C
Quick Check:
PVC waits for matching PV, does not auto-create or delete [OK]

Quick Trick: PVC stays Pending if no matching PV exists [OK]

Common Mistakes:

Thinking Kubernetes auto-creates PVs for PVCs
Assuming pods start without volumes if PVC is unbound
Believing PVCs get deleted automatically when unbound

Master "Persistent Storage" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kubernetes Quizzes

Consider this PersistentVolumeClaim YAML:

Step 1: PVC binding process

Step 2: Behavior when no PV matches

Final Answer:

Quick Check:

Want More Practice?