KCNA Kubernetes Fundamentals Practice Question
Your application requires persistent storage that must be available across pod restarts and rescheduling. What is the recommended approach?
⚠ Common exam trap
Test-takers frequently confuse emptyDir or hostPath as persistent storage because they survive container restarts within the same pod, but they fail to recognize that these volumes do not survive pod deletion or rescheduling to a different node.
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
✓
Use a PersistentVolumeClaim (PVC) and mount it into the pod
PersistentVolumeClaim (PVC) is the recommended approach because it decouples storage provisioning from pod lifecycle, ensuring data persists across pod restarts and rescheduling. PVCs request storage from a PersistentVolume (PV) that is backed by a physical storage system (e.g., NFS, cloud block storage), and the pod mounts this volume, allowing the data to survive even if the pod is deleted and recreated on a different node.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store data in the container's writable layer
Why it's wrong here
The container's writable layer is destroyed with the container, so nothing persists across restarts or rescheduling. It is tempting because writing to the container filesystem requires no volume configuration and is the correct choice for ephemeral, stateless workloads where data loss is acceptable.
- ✗
Use hostPath volume
Why it's wrong here
A hostPath volume binds data to one node's filesystem, so a pod rescheduled elsewhere loses access to it. It is tempting because hostPath is the correct choice for pods that genuinely need to read node-level resources, such as log agents or monitoring daemons.
- ✗
Use an emptyDir volume
Why it's wrong here
An emptyDir volume is deleted when its pod is removed, so data cannot survive restarts or rescheduling. It is tempting because emptyDir is the correct choice for scratch space, caches or temporary files shared between containers within a single pod's lifetime.
- ✓
Use a PersistentVolumeClaim (PVC) and mount it into the pod
Why this is correct
A PersistentVolumeClaim decouples storage lifecycle from the pod, binding to a PersistentVolume that survives restarts and rescheduling. This satisfies the requirement for persistent storage across pod lifecycles, unlike emptyDir or container filesystem storage, which are ephemeral and tied to the pod's lifetime.
Go deeper
Related to this question
About these practice questions
This KCNA question is part of Courseiva's 930-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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This KCNA 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 KCNA exam.