CKAD Application Deployment Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  To roll back a deployment

  Why it's wrong here

  kubectl rollout status does not perform any changes to the Deployment. Rolling back to a previous revision is done with `kubectl rollout undo deployment/<name>`, which creates a new rollout to an old ReplicaSet. The status command merely reports whether the current update has finished, so it cannot replace undo's role.

• ✓

  To check the current status of a rollout

  Why this is correct

  kubectl rollout status is the correct command to monitor a live rollout's progress. It polls the Deployment's status conditions and prints whether the update is still ongoing, has succeeded, or failed during the process deadline. It's a read-only operation and returns a successful exit code once the rollout has completed.

• ✗

  To view the rollout history

  Why it's wrong here

  The rollout history is retrieved with `kubectl rollout history deployment/<name>`, which lists previous ReplicaSet revisions and the reason for changes. `kubectl rollout status` never inspects past revisions; it only tracks the in-flight update from the current revision to the new one, so it cannot replace history lookup.

• ✗

  To pause a rollout

  Why it's wrong here

  Pausing a rollout is the effect of `kubectl rollout pause deployment/<name>`, which stops the controller from progressing beyond the current ReplicaSet. The status command is purely observational and never alters the deployment's desired state, so it cannot introduce a pause or resume operation.

Go deeper

Related to this question