CV0-004 Deployment Practice Question
A company wants to deploy a Kubernetes application across multiple AWS accounts using a single set of manifests. The team needs to manage the deployment centrally while allowing each account to have its own configuration values (e.g., environment-specific variables). Which approach should the team use?
⚠ Common exam trap
CV0-004 often tests the difference between infrastructure-as-code tools; candidates may choose Terraform workspaces because they think it can template Kubernetes manifests, but Helm is specifically designed for parameterized Kubernetes deployments.
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
✓
Use Helm charts with per-environment values files
Helm charts with per-environment values files allow a single set of Kubernetes manifests (templated) to be deployed across multiple AWS accounts, with each account providing its own configuration values (e.g., environment-specific variables) via separate values files. This enables centralized management of the deployment logic while allowing per-account customization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Terraform workspaces with Kubernetes provider
Why it's wrong here
Terraform workspaces isolate state per workspace but the Kubernetes provider still applies manifests to whichever cluster context is configured, so per-account configuration values are not injected into a shared manifest. Workspaces suit parallel environments sharing one provider configuration, not cross-account manifest parameterisation.
- ✓
Use Helm charts with per-environment values files
Why this is correct
Helm charts separate templated manifests from environment-specific values, so one chart deploys across accounts while each account supplies its own values file. This satisfies the requirement for a single set of manifests with per-account configuration, since overrides are injected at render time rather than duplicated per account.
- ✗
Use CloudFormation StackSets with Kubernetes resources
Why it's wrong here
CloudFormation StackSets deploy AWS resources across accounts, but Kubernetes manifests are not CloudFormation resource types, so the application objects never reach the clusters. StackSets suit rolling out IAM roles or VPCs account-wide, not delivering parameterised Kubernetes workloads.
- ✗
Create separate manifests for each account
Why it's wrong here
Duplicating manifests per account abandons the single-set requirement and central management, since each copy drifts independently. It is tempting because per-account manifests do allow bespoke configuration values; that approach fits wholly divergent deployments, not one manifest with parameterised per-account values.
Go deeper
Related to this question
About these practice questions
One of 834 original CV0-004 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official CompTIA exam blueprint
This CV0-004 practice question is part of Courseiva's free CompTIA 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 CV0-004 exam.