KCNA Kubernetes Fundamentals Practice Question
A developer creates a Pod with a container that writes logs to a file in an emptyDir volume. The Pod is then deleted, and a new Pod is created with the same emptyDir volume definition. What happens to the data in the emptyDir volume?
⚠ Common exam trap
The trap here is assuming that emptyDir data persists if the Pod is rescheduled to the same node, confusing it with hostPath or persistent 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
✓
The data is lost because emptyDir volumes are deleted when the Pod is deleted.
emptyDir volumes are ephemeral and are deleted when the Pod is deleted. They are designed for temporary storage that is shared among containers in a Pod or used as a scratch space. When the Pod is removed, the data is lost, and a new Pod will have a fresh emptyDir volume. This behavior is consistent regardless of whether the new Pod is scheduled to the same node or not.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The data is preserved because emptyDir volumes persist across Pod deletions.
Why it's wrong here
emptyDir volumes are ephemeral and are tied to the Pod's lifecycle. When a Pod is deleted, the emptyDir volume is deleted along with it, and the data is lost. The volume is not preserved across Pod deletions. This option incorrectly suggests that emptyDir provides persistence, which it does not.
- ✓
The data is lost because emptyDir volumes are deleted when the Pod is deleted.
Why this is correct
emptyDir volumes are created when a Pod is assigned to a node and exist as long as that Pod is running on that node. When the Pod is deleted, the emptyDir volume is deleted, and its data is permanently lost. A new Pod with a new emptyDir volume starts with an empty directory. This is the correct behavior for emptyDir volumes.
- ✗
The data is preserved if the emptyDir volume is mounted with a persistentVolumeClaim.
Why it's wrong here
emptyDir volumes cannot be backed by a persistentVolumeClaim. They are a separate volume type that provides temporary storage. If you need persistent storage, you would use a PersistentVolumeClaim directly, not an emptyDir. This option confuses emptyDir with persistent storage mechanisms.
- ✗
The data is preserved if the new Pod is scheduled to the same node.
Why it's wrong here
Even if the new Pod is scheduled to the same node, the emptyDir volume from the previous Pod is deleted when the previous Pod is deleted. The new Pod gets a fresh emptyDir volume. The data is not preserved based on node affinity. This option incorrectly implies that emptyDir data is tied to the node rather than the Pod.
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 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.