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.

• ✗

  helm status frontend --namespace web

  Why it's wrong here

  helm status frontend --namespace web shows the current deployment status of the named release, including whether it is deployed, failed, or pending, and it prints the rendered manifest and test results. It does not provide a chronological list of revisions or their associated changes, so you cannot see the sequence of upgrades, rollbacks, or why the release evolved over time. To inspect that revision history, you must use helm history, which lists each revision with metadata like revision number, chart, app version, status, description, and timestamp.

• ✗

  helm list frontend --namespace web

  Why it's wrong here

  helm list frontend --namespace web lists all releases in the namespace, and even when a release name is supplied, it merely displays a single row of top-level information about that release—such as name, status, chart, app version, and the current revision number. This is a snapshot of the latest state, not a history of changes; it has no mechanism to show previous revisions, their values, or the actions that created them. Therefore, it cannot fulfill the need to see revision history, which requires helm history to enumerate each revision record.

• ✗

  helm get manifest frontend --namespace web

  Why it's wrong here

  helm get manifest frontend --namespace web retrieves the Kubernetes YAML manifests that were generated for the release as they are deployed in the cluster. This command returns a static snapshot of the resources for the current revision (or a specific revision if --revision is provided), but it does not give a list of all revisions or timestamps, descriptions, or statuses for historical changes. While it can be used to inspect a particular revision's JSON, it is not the tool for viewing an overview of the release's revision history—that is what helm history offers.

• ✓

  helm history frontend --namespace web

  Why this is correct

  helm history frontend --namespace web is the correct command to display the full revision history for the release named 'frontend' in the 'web' namespace. It outputs a table with each revision number, the chart and app version used, the status (e.g., superseded, failed, deployed), a description of the action (install, upgrade, rollback, or test), and the timestamp of the operation. This provides an audit trail that lets you verify when changes occurred, investigate unexpected behavior, and choose a revision for potential rollback, making it the appropriate command for the question.

Go deeper

Related to this question