KCNA Cloud Native Architecture Practice Question
A development team wants to implement a GitOps workflow for their Kubernetes deployments. Which tool is specifically designed for GitOps on Kubernetes?
⚠ Common exam trap
KCNA often tests the misconception that Helm or Jenkins are GitOps tools, when in fact GitOps requires a dedicated continuous reconciliation controller like ArgoCD or Flux.
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
✓
ArgoCD
ArgoCD is a declarative, GitOps continuous delivery tool for Kubernetes that continuously monitors Git repositories and synchronizes the desired state with the cluster. It is purpose-built for GitOps workflows, automatically detecting drift and applying changes. Helm, Jenkins, and Terraform are not specifically designed for GitOps on Kubernetes.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
ArgoCD
Why this is correct
ArgoCD is purpose-built for GitOps on Kubernetes, continuously reconciling cluster state against a Git repository as the single source of truth. It satisfies the stated GitOps workflow requirement natively, unlike generic CI/CD tools that push changes without declarative drift detection.
- ✗
Helm
Why it's wrong here
Helm packages and templates Kubernetes manifests for installation and upgrades, but it does not watch a Git repository or reconcile drift automatically. It suits managing release versions of charted applications. GitOps requires continuous pull-based synchronisation from Git, which Helm alone does not perform.
- ✗
Jenkins
Why it's wrong here
Jenkins runs pipeline jobs that push changes to a cluster on triggers, so it executes deployments rather than continuously reconciling cluster state with Git. It suits CI build, test and deployment orchestration. GitOps needs a pull-based controller watching the repository, which Jenkins lacks natively.
- ✗
Terraform
Why it's wrong here
Terraform provisions infrastructure declaratively but does not continuously reconcile a Kubernetes cluster against a Git repository; it applies state on invocation. It suits provisioning cloud resources and cluster infrastructure. GitOps requires an in-cluster agent that watches Git and self-heals drift, which Terraform does not provide.
Go deeper
Related to this question
Learn chapter
Cluster Architecture and Lifecycle Management
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.
Key term
ReplicaSet and Replication
A ReplicaSet ensures a specified number of identical pod instances are running at all times in Kubernetes, using replication to maintain availability and stability.
About these practice questions
One of 930 original KCNA 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 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.