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 a Helm library chart and how does it differ from an application chart?

    Answer: A chart that provides reusable templates but deploys no Kubernetes resources itself

    Library charts (type: library in Chart.yaml) define shared template helpers for other charts to use but cannot be installed directly because they produce no manifests.

  2. What happens to Helm release history when `helm uninstall` is run without the `--keep-history` flag?

    Answer: All Kubernetes resources and the release history are permanently deleted

    Without `--keep-history`, `helm uninstall` removes both the deployed Kubernetes resources and the release history Secrets, making rollback impossible.

  3. Which Helm template function should be used instead of `include` when you need to pipe the result through other functions?

    Answer: include

    `include` returns the rendered string so it can be piped (e.g., `include "mytemplate" . | indent 4`), whereas `template` outputs directly and cannot be piped.

  4. What is the role of `helm lint` in chart development?

    Answer: Statically checks a chart for common errors, misconfigurations, and best-practice violations

    `helm lint` performs static analysis on a chart directory, reporting errors and warnings about structure, required fields, and template issues before deployment.

  5. When using `helm upgrade` with `--atomic`, what occurs if the upgrade fails?

    Answer: The upgrade is automatically rolled back to the previous successful release

    `--atomic` combines `--wait` with automatic rollback: if any resource fails to become ready within the timeout, Helm rolls the release back to its previous revision.

  6. How does Helm differentiate between the chart version and the application version it packages?

    Answer: Chart.yaml has a `version` field for the chart and an `appVersion` field for the application

    `Chart.yaml` uses `version` to track the chart's own release cadence and `appVersion` as an informational field indicating the upstream application version being packaged.

  7. What is the purpose of the `helm test` command?

    Answer: Runs test hook Pods defined in the chart to verify a release is functioning correctly

    `helm test ` executes Pods annotated with `helm.sh/hook: test` to perform post-deployment validation, reporting pass or fail based on Pod exit codes.