When installing a Helm chart, an operator needs to override the default container image tag and replica count chosen by the chart author, without editing the chart's templates. Which Helm concept is designed for supplying these customisations at install or upgrade time?
AChart dependencies, which pull in the required image and replica settings from bundled subcharts.
BValues, supplied through a values file or command-line overrides, which the chart's templates reference when rendering the final manifests.check_circle Correct
CChart hooks, which execute at defined lifecycle points and set the image tag and replica count for the operator.
DThe metadata in Chart.yaml, which the operator edits directly to change the image tag and replica count.
Recognise that Helm values, supplied via a values file or CLI overrides, are the mechanism for customising a chart without editing its templates. Helm templates reference values, so an operator overrides defaults by providing a values file or command-line settings at install or upgrade time; the templates then render manifests using those values rather than the author's defaults.
Why A is wrong: Tempting because dependencies do influence what a chart installs, but they declare other charts to include, not per-install overrides of image tag or replica count.
Why B is correct: Correct because values are exactly how Helm parameterises a chart, letting an operator override defaults such as image tag and replica count without touching the templates.
Why C is wrong: Tempting because hooks are a real Helm feature, but they run jobs at lifecycle events and are not the mechanism for supplying configuration overrides.
Why D is wrong: Tempting because Chart.yaml is a core chart file, but it holds chart metadata like name and version, not the configurable values consumed by templates.
Answers that look right on this material and are not. Each one is a distractor from a different question in the KCNA bank for this domain.
Kustomize overlays that patch a shared base of plain manifests per environment
errorWhy it is wrong: Tempting because Kustomize also produces per-environment variants from a shared base, but it is template-free and applies strategic-merge patches rather than substituting placeholders from a values file, so it does not match the stated placeholder-and-values workflow.
A chart, because each installation of the package produces a separate chart in the cluster.
errorWhy it is wrong: Tempting because the word chart is central to Helm, but a chart is the package of templates and defaults, not the installed instance.
A Secret encrypts its data with a per-cluster key by default, whereas a ConfigMap always stores its values in plaintext.
errorWhy it is wrong: Tempting because the word Secret implies confidentiality, but base64 is encoding, not encryption, and Secrets are only encrypted at rest when encryption at rest is explicitly configured for the cluster.