Courseiva
Storage →easyMultiple Choice

CKA Storage Practice Question

A PersistentVolumeClaim named 'my-pvc' is created and remains in 'Pending' state. Which command should the administrator use to investigate the reason?

⚠ Common exam trap

Many exam-takers confuse `get` with `describe`, assuming `get -o yaml` shows all details, but `describe` is the standard troubleshooting command for surfacing events and human-readable error messages that `get` omits.

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

✓

kubectl describe pvc my-pvc

`kubectl describe pvc my-pvc` provides detailed events and status information for the PVC, including any errors or conditions that prevent it from binding to a PersistentVolume (PV). A 'Pending' state typically indicates that the PVC cannot find a matching PV or that the storage class is not available, and the describe command surfaces these reasons in the 'Events' section.

Answer analysis

Option-by-option breakdown

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

  • ✗

    kubectl get pv

    Why it's wrong here

    While this command lists the cluster-wide PersistentVolumes, it does not target the specific PersistentVolumeClaim (my-pvc) or reveal why it remains unbound. It lacks the granular event logs and status conditions of the claim itself, which are critical for diagnosing provisioning or binding failures.

  • ✗

    kubectl get pvc my-pvc -o yaml

    Why it's wrong here

    This command outputs the current configuration and status block of the PVC in YAML format, but it lacks the real-time event stream generated by the control plane. To diagnose why a claim is stuck in a Pending state, you need the detailed scheduler or volume-provisioner events, which are omitted from this structured YAML output.

  • ✗

    kubectl describe pod my-pvc

    Why it's wrong here

    This command fails because it attempts to query a Pod resource named my-pvc instead of the PersistentVolumeClaim. Since my-pvc is a storage claim and not a workload instance, the API server will return a 'not found' error, providing no diagnostic information about the storage issue.

  • ✓

    kubectl describe pvc my-pvc

    Why this is correct

    This is the correct command because it retrieves detailed metadata, status conditions, and the event log specifically for the my-pvc claim. The events section will explicitly show errors such as missing StorageClasses, dynamic provisioning failures, or selector mismatches that explain why the PVC remains unbound.

Quick reference

AWS S3 Storage Class Comparison

Storage ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

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.