Courseiva
Storage →hardMultiple Choice

CKA Storage Practice Question

An administrator needs to configure dynamic provisioning for persistent volumes using an external CSI driver. Which of the following is the correct approach?

⚠ Common exam trap

Test-takers frequently think installing the CSI driver alone is sufficient for dynamic provisioning (Option B), but they miss the critical requirement of creating a StorageClass that explicitly links the PVC request to the CSI driver's provisioner name.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Create a StorageClass with 'provisioner' set to the CSI driver name.

Dynamic provisioning in Kubernetes requires a StorageClass object that references the CSI driver as its provisioner. When a PVC requests a StorageClass with a CSI provisioner, the CSI external-provisioner sidecar automatically creates a PersistentVolume and binds it to the PVC. Without the StorageClass, Kubernetes has no way to know which CSI driver should handle the provisioning request.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Set the 'volumeBindingMode' to 'Immediate' in the PVC.

    Why it's wrong here

    The 'volumeBindingMode' parameter is a configuration field defined exclusively within a 'StorageClass' resource, not a 'PersistentVolumeClaim' (PVC). Furthermore, setting this field to 'Immediate' merely controls when volume binding and provisioning occur (immediately upon PVC creation rather than waiting for pod scheduling), but it does not configure the underlying dynamic provisioning mechanism itself.

  • ✗

    Install the CSI driver and then all PVCs will automatically be provisioned.

    Why it's wrong here

    Simply deploying a Container Storage Interface (CSI) driver to the cluster is insufficient for automatic volume creation. Kubernetes requires a 'StorageClass' resource to act as the administrative blueprint, mapping PVC requests to the installed CSI driver via its 'provisioner' field. Without this resource, the control plane cannot determine which driver or parameters to use when a PVC is created.

  • ✓

    Create a StorageClass with 'provisioner' set to the CSI driver name.

    Why this is correct

    To enable dynamic provisioning, you must define a 'StorageClass' object where the 'provisioner' field matches the registered name of your CSI driver. When a user submits a 'PersistentVolumeClaim' referencing this 'StorageClass', the Kubernetes volume controller automatically invokes the specified CSI driver to provision the underlying storage asset and create the corresponding 'PersistentVolume' on demand.

  • ✗

    Create a PersistentVolume with the CSI driver name in the 'csi' section.

    Why it's wrong here

    Manually defining a 'PersistentVolume' (PV) with a 'csi' block represents static provisioning, where an administrator pre-allocates a specific physical storage asset. Dynamic provisioning explicitly avoids manual PV creation; instead, the system automatically generates the PV resource in response to a PVC request by utilizing a designated 'StorageClass'.

Go deeper

Related to this question

About these practice questions

This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This CKA practice question is part of Courseiva's free CNCF certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CKA exam.