mediumMultiple Choice
200-901 PersistentVolume (PV) Practice Question
A developer wants to deploy a containerized application on a Cisco Container Platform (CCP) cluster. The application requires persistent storage. Which Kubernetes resource should be used to provision storage?
⚠ Common exam trap
Candidates often confuse ConfigMap with PersistentVolumeClaim because both can be mounted into pods. However, ConfigMap is only for configuration data and does not provide persistent storage; PersistentVolumeClaim is the correct resource for requesting storage that survives pod restarts.
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
✓
PersistentVolumeClaim
PersistentVolumeClaim (PVC) is the correct Kubernetes resource for requesting persistent storage. A PVC binds to a PersistentVolume (PV) that provides storage independent of pod lifecycle. ConfigMap is for configuration data, not persistent storage. Secrets store sensitive data, Services enable network access, and neither provides persistent storage.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Secret
Why it's wrong here
A Secret holds sensitive data such as passwords or tokens, base64-encoded, for pods to reference; it does not provision storage. It is tempting because Secrets are also mounted as volumes, but that mount delivers credential files, not a PersistentVolume bound through a PersistentVolumeClaim.
- ✗
Service
Why it's wrong here
A Service provides stable network access to a set of pods; it does not provision or attach storage volumes. It is tempting because Services are core Kubernetes resources, but they address load balancing and discovery. PersistentVolumeClaim is the resource that requests storage from a StorageClass.
- ✓
PersistentVolumeClaim
Why this is correct
A PersistentVolumeClaim requests storage from a StorageClass, which dynamically provisions a PersistentVolume that outlives the pod. Binding the claim to the deployment's pod spec gives the application persistent storage across restarts, matching the stem's requirement on the CCP cluster.
- ✗
ConfigMap
Why it's wrong here
ConfigMap stores non-confidential configuration data as key-value pairs for pods to consume; it cannot provision storage volumes. It is tempting because ConfigMaps are commonly mounted into containers, but that mounting supplies files, not persistent block or file storage backed by a PersistentVolume.
Go deeper
Related to this question
About these practice questions
Courseiva writes every 200-901 question from scratch — 975 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This 200-901 practice question is part of Courseiva's free Cisco 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 200-901 exam.