CKA Storage Practice Question
A Pod is configured with a volume that uses a ConfigMap. The ConfigMap is updated after the Pod is running. How can the Pod access the updated data without restarting?
⚠ Common exam trap
The CKA exam often tests the misconception that ConfigMap updates require a Pod restart, but the trap here is that candidates forget that volume mounts are automatically updated by the kubelet, while environment variable references are not.
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 Pod will automatically see the updated data within minutes.
When a ConfigMap is mounted into a Pod as a volume (without using subPath), updates to the ConfigMap are automatically reflected in the Pod's filesystem after a short delay (typically within minutes, controlled by the kubelet's sync period). However, if the ConfigMap is consumed via environment variables or mounted using subPath, the Pod must be restarted to see the changes. In this question, the volume uses a ConfigMap (presumably without subPath), so the Pod will automatically see the updated data within minutes.
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 ConfigMap must be deleted and recreated.
Why it's wrong here
Deleting and recreating the ConfigMap is unnecessary and can cause temporary data loss or mount errors if the Pod attempts to access the volume during the recreation window. Instead, you can modify the existing ConfigMap in-place using `kubectl edit` or `kubectl apply`, and the kubelet will safely propagate these changes to the mounted volume.
- ✗
The Node must be rebooted.
Why it's wrong here
Rebooting a Kubernetes node is a highly disruptive action that evicts all running workloads and is completely unrelated to volume synchronization. The kubelet daemon running on the node handles the periodic polling and updating of projected volume sources like ConfigMaps entirely in the background without requiring any system-level restarts.
- ✓
The Pod will automatically see the updated data within minutes.
Why this is correct
When a ConfigMap is mounted as a standard volume, the kubelet periodically synchronizes the local files on the node with the updated API resource. This reconciliation loop occurs automatically, typically within a few minutes, depending on the kubelet's sync period and cache propagation delay, without requiring any manual intervention.
- ✗
The Pod must be deleted and recreated.
Why it's wrong here
Recreating the Pod is only necessary if the ConfigMap is injected via environment variables or mounted using a `subPath` volume attachment, which do not receive live updates. For standard volume mounts, the kubelet updates the symlinks pointing to the new data payload automatically, allowing the running container to read the fresh configuration without a restart.
Go deeper
Related to this question
About these practice questions
One of 726 original CKA 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 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.