KCNA Kubernetes Fundamentals Practice Question
A developer creates a Pod with a single container that writes data to /data. The Pod spec includes a volume of type hostPath with path /mnt/data. After the Pod is deleted, the developer notices that the data persists on the node. What is the primary reason for this behavior?
⚠ Common exam trap
The trap here is assuming that all volumes are deleted with the Pod, or that hostPath volumes behave like emptyDir volumes.
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
✓
hostPath volumes are not deleted when the Pod is deleted; they persist on the node's filesystem.
hostPath volumes directly mount a node's filesystem path into a Pod. Data written to that path is stored on the node and remains there even after the Pod is deleted. This is why the data persists, as the node's directory is not automatically cleaned up by Kubernetes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
hostPath volumes are not deleted when the Pod is deleted; they persist on the node's filesystem.
Why this is correct
hostPath volumes mount a file or directory from the host node's filesystem into the Pod. The data written to the hostPath persists beyond the Pod's lifecycle because it is stored on the node itself. Deleting the Pod does not remove the host directory or its contents.
- ✗
The Pod's restartPolicy is set to Always, which causes the volume to be recreated after deletion.
Why it's wrong here
restartPolicy controls container restarts within a Pod, not volume persistence. Even with Always, when the Pod is deleted, the hostPath volume remains because it is tied to the node, not the Pod. The policy does not affect volume lifecycle.
- ✗
The volume is backed by a PersistentVolume that retains data even after the Pod is deleted.
Why it's wrong here
A PersistentVolume is a separate resource with its own lifecycle and reclaim policy. The scenario describes a hostPath volume, not a PersistentVolume. hostPath volumes are ephemeral from the Pod's perspective but persistent on the node's filesystem.
- ✗
The kubelet caches volume data in memory and writes it back to the hostPath after Pod deletion.
Why it's wrong here
The kubelet does not cache volume data in memory for hostPath volumes. Data is written directly to the host's filesystem. There is no write-back mechanism; the persistence is simply because the host directory is not cleaned up when the Pod is removed.
Go deeper
Related to this question
About these practice questions
One of 930 original KCNA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CNCF exam blueprint
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.