Courseiva
Workloads and Scheduling →easyMultiple Choice

CKA Workloads and Scheduling Practice Question

Which command retrieves the rollout history of a Deployment named 'web'?

⚠ Common exam trap

The CKA exam often tests the distinction between commands that show current state (`describe`, `status`) versus those that show historical data (`rollout history`), leading candidates to confuse `rollout status` with `rollout history`.

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 history deployment web

The `kubectl rollout history deployment web` command retrieves the revision history of the specified Deployment, showing each revision number and, with the `--revision` flag, the details of a specific revision. This is the standard Kubernetes command for viewing rollout history, as defined in the kubectl reference.

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 describe deployment web

    Why it's wrong here

    `kubectl describe deployment web` prints the Deployment's spec, status, labels, selector, replica counts, conditions, and recent events as a snapshot of the current desired and observed state. It does not enumerate or number the revisions created by previous rollouts, and it cannot show the change-cause annotations or pod templates of past revisions, so it is not a source of rollout history.

  • ✗

    kubectl get events --field-selector involvedObject.name=web

    Why it's wrong here

    `kubectl get events --field-selector involvedObject.name=web` filters Kubernetes Events whose involved object name is exactly `web`; these are ephemeral, timestamped records of actions like scaling, pulls, or replica-set changes. Events are periodically pruned by the cluster and are not stored as a structured revision history, whereas rollout history is derived from the persistent chain of ReplicaSets managed by the Deployment controller, each carrying a revision annotation.

  • ✓

    kubectl rollout history deployment web

    Why this is correct

    `kubectl rollout history deployment web` is the dedicated subcommand that lists all historical rollouts for Deployment `web`, displaying a table of revisions with their change causes (e.g., `REVISION CHANGE-CAUSE`). Internally it reads the Deployment's managed ReplicaSets and their `deployment.kubernetes.io/revision` annotations; with `--revision=N` it can also show the complete pod template for a specific revision, making it the correct command to view rollout history.

  • ✗

    kubectl rollout status deployment web

    Why it's wrong here

    `kubectl rollout status deployment web` monitors the live progress of the current rollout and blocks until the deployment finishes successfully, times out, or fails, with messages like `deployment "web" successfully rolled out`. It is concerned only with the in-progress or current state of the rollout, not with enumerating past revision numbers or their change causes, so it cannot answer a question about historical rollouts.

About these practice questions

This CKA question is part of Courseiva's 726-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This CKA 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 CKA exam.