Bird
0
0

You want to update a ConfigMap mounted as a volume in a running pod. What happens to the files inside the container?

hard📝 Application Q9 of 15
Kubernetes - ConfigMaps
You want to update a ConfigMap mounted as a volume in a running pod. What happens to the files inside the container?
AFiles remain unchanged until the pod is restarted
BFiles are updated automatically within a few seconds
CFiles are deleted and recreated immediately
DPod crashes due to ConfigMap update
Step-by-Step Solution
Solution:

  1. Step 1: Understand ConfigMap volume update behavior

    Kubernetes automatically updates mounted ConfigMap files inside running pods within seconds after ConfigMap changes.

  2. Step 2: Exclude other behaviors

    Files do not require pod restart, are not deleted/recreated abruptly, and pod does not crash due to ConfigMap update.

  3. Final Answer:

    Files are updated automatically within a few seconds -> Option B

  4. Quick Check:

    ConfigMap volume files auto-update in running pods [OK]
Quick Trick: ConfigMap volume files auto-update in running pods [OK]
Common Mistakes:
  • Thinking pod restart is needed to see changes
  • Assuming files are deleted and recreated abruptly
  • Believing pod crashes on ConfigMap update

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Updating ConfigMaps and propagation - Quiz 6medium ConfigMaps - Using ConfigMaps as environment variables - Quiz 15hard Networking - Why Kubernetes networking matters - Quiz 2easy Resource Management - Cluster Autoscaler concept - Quiz 4medium Scheduling - Pod affinity and anti-affinity - Quiz 13medium Scheduling - Why scheduling controls Pod placement - Quiz 4medium Scheduling - Pod affinity and anti-affinity - Quiz 2easy Scheduling - Jobs and CronJobs for batch processing - Quiz 9hard Secrets - Secret types (Opaque, docker-registry, TLS) - Quiz 7medium Secrets - Using Secrets as mounted volumes - Quiz 3easy