KCNA Cloud Native Architecture Practice Question
An organization uses GitOps with ArgoCD to manage Kubernetes deployments. What is the PRIMARY advantage of this approach over traditional imperative deployment methods?
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
✓
It provides a single source of truth for cluster state through Git
GitOps uses a Git repository as the single source of truth, enabling declarative configuration, version control, and automated reconciliation. This is the primary advantage over traditional imperative methods. Option A is incorrect because manual approval processes can still be part of a GitOps workflow. Option C is incorrect because GitOps does not eliminate the need for access controls. Option D is incorrect because GitOps does not directly reduce container count.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
It eliminates the need for any manual approval processes
Why it's wrong here
ArgoCD reconciles cluster state to Git continuously, but manual approval gates can still be configured in the pipeline; GitOps does not remove them. It is tempting because declarative Git history enables auditable change control, which in regulated environments would be the correct fit.
- ✓
It provides a single source of truth for cluster state through Git
Why this is correct
Git holds the declarative desired state, and ArgoCD continuously reconciles the cluster to match it. This differs from imperative scripting, which issues one-off commands, because Git becomes the authoritative, auditable source of truth for the cluster.
- ✗
It allows developers to directly access the Kubernetes cluster
Why it's wrong here
ArgoCD reconciles cluster state from Git; it does not grant developers direct cluster access, and doing so would bypass the Git workflow entirely. It is tempting because developers interact with deployments, but the benefit is declarative, auditable synchronisation rather than direct kubectl access.
- ✗
It reduces the number of containers needed in a deployment
Why it's wrong here
GitOps changes how desired state is declared and reconciled, not how many containers a workload runs; container count is set by the manifests themselves. It is tempting because declarative tooling can simplify manifests, but the advantage is automated reconciliation from Git, not fewer containers.
Go deeper
Related to this question
Learn chapter
Container Orchestration Essentials
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
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 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.