nerdexam
Linux_Foundation

KCNA · Question #3

What is the core functionality of GitOps tools like Argo CD and Flux?

The correct answer is D. They continuously compare the desired state in Git with the actual production state and notify or. GitOps tools like Argo CD and Flux continuously synchronize the live state of a cluster with a desired state defined in a Git repository, flagging or correcting any deviations.

Submitted by yuriko_h· May 4, 2026Cloud Native Application Delivery

Question

What is the core functionality of GitOps tools like Argo CD and Flux?

Options

  • AThey track production changes made by a human in a Git repository and generate a human-
  • BThey replace human operations with an agent that tracks Git commands.
  • CThey automatically create pull requests when dependencies are outdated.
  • DThey continuously compare the desired state in Git with the actual production state and notify or

How the community answered

(25 responses)
  • A
    4% (1)
  • C
    4% (1)
  • D
    92% (23)

Why each option

GitOps tools like Argo CD and Flux continuously synchronize the live state of a cluster with a desired state defined in a Git repository, flagging or correcting any deviations.

AThey track production changes made by a human in a Git repository and generate a human-

While GitOps tracks changes in Git, its core functionality isn't just generating human-readable summaries of human-made changes but enforcing the Git state.

BThey replace human operations with an agent that tracks Git commands.

GitOps replaces manual operations with automated reconciliation based on Git, but it doesn't use an agent to track Git commands in the sense of B.

CThey automatically create pull requests when dependencies are outdated.

Automatically creating pull requests for outdated dependencies is a function of dependency management tools or bots, not the core continuous synchronization principle of GitOps.

DThey continuously compare the desired state in Git with the actual production state and notify orCorrect

GitOps tools operate by continuously observing the desired state of a system, defined declaratively in Git, and comparing it against the actual state of the cluster. If a drift is detected, they either notify or automatically reconcile the cluster's state to match the Git repository, ensuring the system is always in the desired configuration.

Concept tested: GitOps principles and reconciliation

Source: https://fluxcd.io/flux/concepts/

Topics

#GitOps#Argo CD#Flux#Continuous Delivery

Community Discussion

No community discussion yet for this question.

Full KCNA Practice