KCNA Cloud Native Architecture Practice Question
Which of the following best describes the GitOps pattern?
⚠ Common exam trap
CNCF often tests the misconception that GitOps is simply about storing YAML files in Git or using Git as a trigger for CI/CD, when the defining characteristic is the automated reconciliation loop that enforces the 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
✓
Declarative configuration stored in Git, with automated deployment via a controller
GitOps is a pattern where the entire system's desired state is declared in a Git repository, and an automated controller (such as Argo CD or Flux) continuously reconciles the live cluster state with that declarative configuration. This ensures that Git is the single source of truth, and any drift from the declared state is automatically corrected without manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Imperative commands applied to the cluster and tracked in Git
Why it's wrong here
GitOps declares desired state in Git and has a controller continuously reconcile the cluster toward it; imperative commands pushed to the cluster are the opposite of that declarative pull model. It is tempting because Git still stores the commands as an audit trail, but tracking imperative actions in Git is not GitOps.
- ✗
Using Git as a backup for Kubernetes manifests
Why it's wrong here
GitOps treats Git as the single source of truth that a controller continuously reconciles against the cluster, not merely a backup store for manifests. It is tempting because keeping manifests in Git does provide version history and recovery, but passive storage without automated reconciliation does not constitute the GitOps pattern.
- ✗
Using Git hooks to trigger CI/CD pipelines
Why it's wrong here
GitOps relies on a reconciliation controller watching the repository and pulling changes into the cluster, not on Git hooks firing CI/CD pipelines to push updates. It is tempting because hooks and pipelines do automate deployments from commits, but that push-based CI/CD flow is distinct from the GitOps pull-and-reconcile pattern.
- ✓
Declarative configuration stored in Git, with automated deployment via a controller
Why this is correct
GitOps stores the entire desired state declaratively in Git as the single source of truth, and a controller running in the cluster continuously reconciles live state to match it, automating deployment without manual kubectl or pipeline pushes.
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.
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 by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.