Courseiva
← ACE
Full test
mediumMultiple ChoiceObjective-mapped

Google ACE Practice Question: A team packages their Kubernetes application as a…

A team packages their Kubernetes application as a Helm chart. They need to install it into a GKE cluster with the release name 'webapp' in the 'production' namespace, overriding the default image tag to 'v2.1'. Which Helm command achieves this?

⚠ Common exam trap

It's easy for candidates to confuse Helm commands with kubectl or assume a generic 'deploy' verb exists, when Helm strictly uses `install` for first-time deployments and `upgrade` for updates.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

helm install webapp ./chart -n production --set image.tag=v2.1

`helm install` is the standard Helm command to deploy a chart into a cluster, and the `--set` flag overrides default values like `image.tag`. The `-n` flag specifies the namespace, and the release name 'webapp' is given as the first argument. This matches the Helm CLI syntax exactly.

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 deploy webapp ./chart -n production --set image.tag=v2.1

    Why it's wrong here

    There is no `helm deploy` subcommand in Helm's command-line interface. The rest of the syntax is plausible — release name, chart path, namespace, and `--set` override — but the verb is invalid, so Helm will exit with an unknown command error. For an initial deployment you must use `helm install`; if the release already exists, you would use `helm upgrade` (or ideally `helm upgrade --install` for idempotent deployment).

  • ✓

    helm install webapp ./chart -n production --set image.tag=v2.1

    Why this is correct

    This is the correct Helm command. `helm install` is used to deploy a chart for the first time with a given release name (`webapp`), chart path (`./chart`), and target namespace via `-n production`. The `--set image.tag=v2.1` flag overrides the chart's default `image.tag` value, ensuring the deployment uses the v2.1 container image as required.

  • ✗

    kubectl apply -f helm-chart.yaml -n production --image-tag=v2.1

    Why it's wrong here

    This command is invalid because `kubectl apply` is designed for raw Kubernetes manifests (YAML/JSON), not Helm charts. A Helm chart is a directory of templates and values that must first be rendered by Helm into concrete Kubernetes resources; `kubectl` cannot interpret chart structure, nor does it accept an `--image-tag` flag. Even if the file were a rendered manifest, the flag would cause an error, so this would never succeed.

  • ✗

    helm apply webapp -n production --chart=./chart --tag=v2.1

    Why it's wrong here

    `helm apply` is not a subcommand in the Helm CLI; valid verbs include `install`, `upgrade`, `rollback`, `uninstall`, and `status`. The flags `--chart` and `--tag` do not exist; the chart path is passed as a positional argument, and image overrides are specified with `--set key=value`. The correct way to deploy a chart with a custom tag is `helm install webapp ./chart -n production --set image.tag=v2.1`.

About these practice questions

This ACE question is part of Courseiva's 769-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.