KCNA Cloud Native Architecture Practice Question
A development team is adopting a GitOps workflow for their Kubernetes applications. They want to ensure that the cluster state always matches the desired state defined in Git. Which component is responsible for continuously reconciling the cluster with the Git repository?
⚠ Common exam trap
The trap here is assuming that core Kubernetes components like the API server or scheduler handle external Git reconciliation, when in fact GitOps requires a dedicated operator to pull and apply desired state from Git.
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
✓
GitOps operator such as Argo CD or Flux
GitOps relies on an operator like Argo CD or Flux that runs in the cluster and continuously reconciles the live state with the desired state stored in Git. This automated sync ensures that any drift is corrected, providing a declarative and version-controlled deployment model.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
kube-scheduler
Why it's wrong here
The kube-scheduler assigns pods to nodes based on resource requirements and constraints, but it does not interact with Git or manage desired state from external sources. Its role is limited to scheduling decisions within the cluster. It cannot reconcile cluster state with a Git repository, so it is not responsible for GitOps workflows.
- ✓
GitOps operator such as Argo CD or Flux
Why this is correct
A GitOps operator runs in the cluster and continuously monitors the Git repository for changes. It compares the desired manifests with the live cluster state and applies any differences, ensuring reconciliation. This automated sync is the core of GitOps and directly satisfies the requirement for continuous reconciliation with Git.
- ✗
Container runtime
Why it's wrong here
The container runtime, such as containerd, is responsible for running containers on a node. It does not have knowledge of Git repositories or cluster-wide desired state. It operates at the node level under the kubelet's direction. Therefore, it cannot perform the reconciliation between Git and the cluster required for GitOps.
- ✗
Kubernetes API server
Why it's wrong here
The Kubernetes API server exposes the control plane API and stores cluster state, but it does not automatically pull or reconcile with an external Git repository. It responds to requests from controllers and users. Without an external agent, it cannot detect drift from Git, so it does not fulfill the GitOps reconciliation role.
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
This KCNA question is part of Courseiva's 930-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 →
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.