KCNA Cloud Native Architecture Practice Question
Which TWO tools are commonly used for GitOps? (Choose two.)
⚠ Common exam trap
KCNA often tests the confusion between CI tools (Jenkins), package managers (Helm), and GitOps operators; candidates may pick Helm because it is Kubernetes-related, but it is not a GitOps tool.
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
✓
Flux
Flux (A) is a CNCF-graduated GitOps operator that continuously reconciles Kubernetes cluster state with manifests stored in a Git repository, making it a canonical GitOps tool. ArgoCD (E) is likewise a declarative GitOps continuous-delivery controller for Kubernetes that syncs applications from Git and detects drift, so it is also correct. Jenkins (B) is a general-purpose CI automation server; it can trigger GitOps-style pipelines but is not itself a GitOps reconciliation tool. Helm (C) is a Kubernetes package manager for templating and releasing charts, not a GitOps controller. Terraform (D) is an infrastructure-as-code provisioning tool that applies state from configuration, but it is not a GitOps continuous reconciliation engine.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Flux
Why this is correct
Flux continuously reconciles cluster state against a Git repository, automatically applying committed manifests without manual intervention. It satisfies the GitOps requirement for declarative, version-controlled delivery, alongside Argo CD. Flux's pull-based controller architecture detects drift and re-syncs, which is precisely the mechanism the question targets.
- ✗
Jenkins
Why it's wrong here
Jenkins runs imperative pipeline jobs that push changes to clusters; it holds no reconciliation loop comparing desired state in Git against live state, so drift is never corrected automatically. It is tempting because Jenkins is ubiquitous in CI/CD, and it would be correct for building, testing and deploying artefacts rather than continuous GitOps reconciliation.
- ✗
Helm
Why it's wrong here
Helm is a package manager for Kubernetes that deploys applications as pre-configured charts, but it lacks the continuous reconciliation loop that defines GitOps: Helm applies a chart once and does not automatically detect or correct drift between the cluster state and the desired state declared in Git. It is tempting because Helm charts are widely used to define Kubernetes resources, and teams often assume that storing a chart in a Git repository alone constitutes GitOps, whereas a true GitOps tool like Argo CD or Flux continuously synchronises the cluster with the repository.
- ✗
Terraform
Why it's wrong here
Terraform provisions infrastructure from declarative configuration but is invoked manually or via pipelines, and it does not continuously reconcile cluster state against a Git repository. It suits provisioning cloud resources, not GitOps delivery. It is tempting because its declarative, version-controlled approach superficially resembles GitOps.
- ✓
ArgoCD
Why this is correct
ArgoCD continuously reconciles cluster state against declarative manifests stored in Git, automatically syncing drift without manual intervention. This satisfies the GitOps requirement for a pull-based deployment tool, where Git remains the single source of truth and the cluster pulls desired configuration rather than receiving pushed updates.
Visual reference
Go deeper
Related to this question
Learn chapter
Cluster Architecture and Lifecycle Management
Key term
Helm Charts
Helm Charts are packages of pre-configured Kubernetes resources that let you install, upgrade, and manage complex applications on a Kubernetes cluster with a single command.
Key term
GitOps
GitOps is a way to manage and automate cloud infrastructure and applications by using a Git repository as the single source of truth, where all changes are made through pull requests and automatically applied by a software agent.
About these practice questions
Courseiva writes every KCNA question from scratch — 930 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. 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 CNCF exam blueprint
This KCNA practice question is part of Courseiva's free CNCF 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 KCNA exam.