KCNA Helm and Package Management 3

Question 1

What is a Helm 'hook' and when is it executed?

Accepted Answer

An annotation-driven Kubernetes resource executed at specific points in a release lifecycle

Answer

Helm hooks are Kubernetes manifests annotated with `helm.sh/hook` that run at lifecycle points such as pre-install, post-install, pre-upgrade, or pre-delete.

Question 2

Which `helm` subcommand displays the values currently applied to a deployed release?

Accepted Answer

helm get values

Answer

`helm get values <release>` retrieves the user-supplied values for a running release; adding `--all` also shows computed defaults.

Question 3

What is the effect of setting `helm.sh/hook-delete-policy: before-hook-creation` on a hook resource?

Accepted Answer

Deletes the previous hook resource before creating a new one on the next run

Answer

The `before-hook-creation` policy tells Helm to delete the existing hook resource before creating a fresh one, preventing conflicts on re-runs.

Question 4

Which file in a Helm chart directory contains metadata such as the chart name, version, and description?

Accepted Answer

Chart.yaml

Answer

`Chart.yaml` is the mandatory metadata file that declares the chart's name, version, type, description, and other top-level properties.

Question 5

When using `helm upgrade --install`, what happens if the specified release does not yet exist?

Accepted Answer

Helm performs an initial installation instead of an upgrade

Answer

`--install` makes `helm upgrade` idempotent: if the release doesn't exist it is installed; if it does, it is upgraded.

(KCNA) Kubernetes and Cloud Native Associate Practice Test

(KCNA) Kubernetes and Cloud Native Associate Practice Test

KCNA Helm and Package Management 3