KCNA Cloud Native Application Delivery Practice Question
A DevOps team wants to implement GitOps for their Kubernetes cluster. Which tool is specifically designed for Kubernetes GitOps and can automatically sync the cluster state with a Git repository?
⚠ Common exam trap
KCNA often tests the confusion between GitOps tools (ArgoCD, Flux) and Kubernetes packaging/config tools (Helm, Kustomize) — candidates pick Helm or Kustomize because they are Kubernetes-related but not GitOps reconcilers.
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 designed specifically for Kubernetes. It continuously monitors a Git repository and automatically syncs the cluster state to match the desired state defined in Git, making it the correct choice for Kubernetes GitOps.
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 a declarative GitOps continuous delivery controller built specifically for Kubernetes. It continuously reconciles live cluster state against manifests stored in Git, automatically syncing drift back to the declared desired state, which directly satisfies the requirement for automatic cluster-to-repository synchronisation.
- ✗
Jenkins
Why it's wrong here
Jenkins is a general-purpose CI server that runs pipeline jobs on triggers; it has no built-in agent watching a Git repository and continuously reconciling live cluster state to match it. It is tempting because it is a familiar automation tool, and it would be correct for building, testing and deploying artefacts rather than GitOps reconciliation.
- ✗
Kustomize
Why it's wrong here
Kustomize renders and overlays Kubernetes YAML manifests but runs only when invoked by a pipeline or kubectl; it holds no reconciliation loop and never watches a Git repository to sync cluster state. It is tempting because it is Kubernetes-native configuration tooling, and it would be correct for templating environment-specific manifests without Helm charts.
- ✗
Helm
Why it's wrong here
Helm packages and templates Kubernetes manifests for installation and upgrades, but it does not continuously watch a Git repository and reconcile drift back into the cluster. It is tempting because it is Kubernetes-native and Git-friendly, and it would be correct for managing releases and chart versioning rather than autonomous GitOps synchronisation.
Go deeper
Related to this question
Learn chapter
Cluster Architecture and Lifecycle Management
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.
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.