[Solved] Given this StorageClass YAML snippet:apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: slow provisioner: kubernetes.io/no-provisioner volumeBindingMode:... | Kubernetes

Kubernetes - Persistent Storage

Given this StorageClass YAML snippet:

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: slow
provisioner: kubernetes.io/no-provisioner
volumeBindingMode: WaitForFirstConsumer
reclaimPolicy: Retain

What will happen when a PersistentVolumeClaim requests storage from this class?

AThe volume will not be dynamically provisioned; manual provisioning is required

BThe volume will be deleted automatically when released

CThe volume will be dynamically provisioned immediately

DThe volume will be provisioned but bound immediately without waiting

Step-by-Step Solution

Solution:

Step 1: Analyze provisioner field
The provisioner is kubernetes.io/no-provisioner, meaning no dynamic provisioning.
Step 2: Understand reclaimPolicy and binding mode
ReclaimPolicy is Retain (volume kept after release), and volumeBindingMode waits for pod scheduling.
Final Answer:
The volume will not be dynamically provisioned; manual provisioning is required -> Option A
Quick Check:
No provisioner = manual provisioning [OK]

Quick Trick: No provisioner means no dynamic provisioning [OK]

Common Mistakes:

Assuming dynamic provisioning happens with no-provisioner
Confusing reclaimPolicy with provisioning behavior
Ignoring volumeBindingMode effect

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

Given this StorageClass YAML snippet:

Step 1: Analyze provisioner field

Step 2: Understand reclaimPolicy and binding mode

Final Answer:

Quick Check:

Want More Practice?