DCA Question #67: Real Exam Question with Answer & Explanation

The correct answer is B: No. Specifying a default provisioner and creating a PersistentVolumeClaim are not sufficient for dynamic provisioning; a default StorageClass must also be defined.

Submitted by diego_uy· Apr 18, 2026Storage and Volumes

Question

Are these conditions sufficient for Kubernetes to dynamically provision a persistentVolume, assuming there are no limitations on the amount and type of available external storage? Solution: A default provisioner is specified, and subsequently a persistentVolumeClaim is created.

Options

AYes
BNo

Explanation

Specifying a default provisioner and creating a PersistentVolumeClaim are not sufficient for dynamic provisioning; a default StorageClass must also be defined.

Common mistakes.

A. Simply having a provisioner configured somewhere is not enough; the PersistentVolumeClaim needs to associate with a StorageClass (either explicitly or via a default) that uses that provisioner to initiate dynamic provisioning.

Concept tested. Kubernetes dynamic PersistentVolume provisioning

Reference. https://kubernetes.io/docs/concepts/storage/persistent-volumes/#dynamic

Topics

#Kubernetes Storage#PersistentVolumes#Dynamic Provisioning#StorageClass

Community Discussion

No community discussion yet for this question.

Full DCA Practice Browse All DCA Questions