Practice Test Geeks(KCNA) Kubernetes and Cloud Native Associate Practice Test
← All KCNA Flashcard Decks

Helm and Package Management Flashcards

7 cards from real KCNA practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 7 Helm and Package Management flashcards as text

  1. What is the difference between `helm install` and `helm upgrade` when the `--force` flag is used?

    Answer: --force deletes and re-creates resources that cannot be patched in place

    `--force` causes Helm to delete and recreate resources that fail a standard patch/update, useful when resource specs have immutable fields that changed.

  2. How can you override a nested value in values.yaml from the `helm install` command line?

    Answer: --set parent.child=value

    `--set` accepts dot-notation paths such as `parent.child=value` to override nested keys in values.yaml without editing the file.

  3. What is an OCI registry in the context of Helm charts?

    Answer: A container image registry used to store and distribute Helm charts as OCI artifacts

    Helm supports storing charts in OCI-compliant registries (like Docker Hub or ECR) as artifacts, using `helm push` and `helm pull oci://` references.

  4. Which Helm command packages a chart directory into a versioned `.tgz` archive for distribution?

    Answer: helm package

    `helm package` compresses a chart directory into a `-.tgz` tarball that can be uploaded to a chart repository or OCI registry.

  5. What is the purpose of the `NOTES.txt` file in a Helm chart's `templates/` directory?

    Answer: Rendered and displayed to the user after a successful install or upgrade

    `NOTES.txt` is a template rendered after install/upgrade and printed to the user's terminal, typically containing usage instructions or next steps.

  6. What Helm concept allows one chart to include and manage other charts as dependencies?

    Answer: Subcharts

    Subcharts (also called child charts) are charts listed under `dependencies` in Chart.yaml and packaged inside the parent chart's `charts/` directory.

  7. Which annotation marks a Kubernetes resource so Helm adopts management of it even if not originally installed by Helm?

    Answer: meta.helm.sh/release-name and meta.helm.sh/release-namespace

    Setting both `meta.helm.sh/release-name` and `meta.helm.sh/release-namespace` annotations (along with `app.kubernetes.io/managed-by: Helm` label) tells Helm to adopt an existing resource.