Courseiva
Application Deployment →mediumMultiple Choice

CKAD Application Deployment Practice Question

You manage a Deployment named 'web' in namespace 'prod' whose pods mount a ConfigMap named 'web-config' as a volume at /etc/web. You update the ConfigMap data, but the running pods still serve the old configuration because the application only reads the mounted file at startup. You must roll out the new configuration to all pods with zero downtime and preserve the ability to roll back. What is the MOST appropriate action?

⚠ Common exam trap

The trap here is assuming that because mounted ConfigMap volumes are eventually updated on disk, the application will automatically pick up new values without any pod restart.

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

✓

Run 'kubectl rollout restart deployment/web -n prod', which adds a restartedAt annotation to the pod template and triggers a new revision.

A rollout restart is the standard CKAD pattern for forcing pods to reload configuration that is consumed only at process start. It creates a new ReplicaSet revision by mutating the pod template annotation, so the rolling update proceeds with zero downtime and the previous ReplicaSet remains for rollback. Deleting the ConfigMap, changing the image, or manually signaling processes do not produce a clean, reversible rollout.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Edit the Deployment and change the container image tag to a new value, forcing Kubernetes to recreate all pods with the refreshed ConfigMap.

    Why it's wrong here

    Changing the image tag does trigger a rollout, but it also deploys a different application version than the one currently running. This conflates a configuration refresh with an application upgrade, may introduce unrelated behavior changes, and is unnecessary when the only intended change is to pick up new ConfigMap data. The scenario does not mention a new image.

  • ✗

    Use 'kubectl exec' into each pod and run a command to signal the application process to re-read /etc/web, then wait for the kubelet to sync the volume.

    Why it's wrong here

    Manually signaling each pod is operationally fragile, does not update the Deployment's pod template, and creates no new revision, so kubectl rollout undo cannot revert it. It also assumes application-specific signal handling that may not exist, and any pod that restarts later would still load the old cached configuration until the next ConfigMap change.

  • ✗

    Delete the ConfigMap and recreate it with the updated data so the kubelet re-syncs the projected volume contents immediately.

    Why it's wrong here

    Deleting and recreating the ConfigMap does not trigger any pod restart, and the application still reads the file only at startup, so pods continue serving stale values. Additionally, deleting the ConfigMap can break new pods that mount it before it is recreated, and no Deployment revision is recorded, so there is no rollout history to undo.

  • ✓

    Run 'kubectl rollout restart deployment/web -n prod', which adds a restartedAt annotation to the pod template and triggers a new revision.

    Why this is correct

    Running kubectl rollout restart patches the Deployment's pod template with a kubectl.kubernetes.io/restartedAt annotation, creating a new ReplicaSet revision. Because volume-mounted ConfigMaps are refreshed asynchronously but the app reads only at startup, restarting pods forces them to load the new values. The old ReplicaSet is retained, so kubectl rollout undo remains available for rollback.

About these practice questions

Courseiva writes every CKAD question from scratch — 826 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

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 CKAD 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 CKAD exam.