CKAD Application Deployment Practice Question
You have a Deployment that is currently paused. You want to resume the rollout and then check the status of the rollout. Which set of commands should you run?
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
✓
kubectl rollout resume deployment/myapp && kubectl rollout status deployment/myapp
First, resume the rollout with 'kubectl rollout resume deployment/<name>', then check status with 'kubectl rollout status deployment/<name>'. Option D is correct. Option B uses 'kubectl rollout history' which shows revision history, not current status.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
kubectl rollout pause deployment/myapp && kubectl rollout status deployment/myapp
Why it's wrong here
`kubectl rollout pause` sets the deployment's rollout progress to a paused state, which is useful for preventing automatic updates while you make manual changes, but it does not advance the rollout. Combining it with `rollout status` would cause the status command to hang or report a stalled rollout, because the paused controller is not creating or updating any Pods. The question asks to resume an already-paused deployment, not to pause it again, so this command pair actively opposes the goal.
- ✗
kubectl rollout resume deployment/myapp && kubectl rollout history deployment/myapp
Why it's wrong here
While `kubectl rollout resume` is the correct first step, `kubectl rollout history` only lists the revision numbers and their change causes — it does not show live rollout progress, replica availability, or deployment conditions. The command returns a static list immediately instead of polling until rollout completion, so it gives no indication of whether the resumed rollout actually finished successfully. To verify the deployment's current status after resuming, you need `kubectl rollout status`, which watches the rollout until it reaches the desired state.
- ✗
kubectl rollout undo deployment/myapp && kubectl rollout status deployment/myapp
Why it's wrong here
`kubectl rollout undo` rolls back to a previous revision, effectively overriding the deployment's current desired state with an older one. The question is about resuming a paused rollout, not about changing the intended revision; undoing would create a brand-new rollout for the old configuration, which is a different operation and could conflict with the paused state. Even if followed by `rollout status`, the status would be for the reverted rollout, not the original paused one, so this pair does not answer the question.
- ✓
kubectl rollout resume deployment/myapp && kubectl rollout status deployment/myapp
Why this is correct
The correct sequence is `kubectl rollout resume` to unpause the deployment, letting the deployment controller continue the rolling update from where it left off, followed by `kubectl rollout status` to poll the rollout until it completes or reports an error. The status command blocks until the rollout condition is successful, giving immediate and accurate feedback on the health of the deployment. This directly addresses the user's intent: resume the paused deployment and confirm it reaches the desired state.
Go deeper
Related to this question
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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.