Bird
0
0

You updated a ConfigMap but your pods still use old values. Which command fixes this without deleting pods manually?

medium📝 Troubleshoot Q14 of 15
Kubernetes - ConfigMaps
You updated a ConfigMap but your pods still use old values. Which command fixes this without deleting pods manually?
Akubectl rollout restart deployment/myapp
Bkubectl delete pod -l app=myapp
Ckubectl apply -f configmap.yaml
Dkubectl configmap refresh myapp
Step-by-Step Solution
Solution:

  1. Step 1: Identify how to refresh pods after ConfigMap update

    Pods must restart to load new ConfigMap values.

  2. Step 2: Use rollout restart to restart pods gracefully

    Command 'kubectl rollout restart' triggers pod restart without manual deletion.

  3. Final Answer:

    kubectl rollout restart deployment/myapp -> Option A

  4. Quick Check:

    Use rollout restart to refresh pods = D [OK]
Quick Trick: Use rollout restart to refresh pods after ConfigMap update [OK]
Common Mistakes:
  • Deleting pods manually instead of rollout restart
  • Expecting apply to restart pods automatically
  • Using non-existent commands like configmap refresh

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Creating ConfigMaps from files - Quiz 13medium Health Checks and Probes - TCP probe configuration - Quiz 10hard Ingress - Path-based routing - Quiz 13medium Ingress - Why Ingress manages external access - Quiz 9hard Networking - DNS in Kubernetes (CoreDNS) - Quiz 13medium Resource Management - Why resource management matters - Quiz 7medium Scheduling - Taints and tolerations - Quiz 14medium Scheduling - Node selectors for simple scheduling - Quiz 15hard Secrets - External secret management integration - Quiz 6medium Secrets - External secret management integration - Quiz 14medium