← CGOA hub

CGOA — GitOps Terminology

20% of the CGOA exam. Sample questions below; the full library has 24 questions tagged to this domain.

Sample questions on GitOps Terminology

GitOps Terminology

Q1. A team uses Argo CD to monitor a Git repository and automatically apply changes to their Kubernetes cluster. In this scenario, what is Argo CD serving as?

Reveal answer and explanations
  1. A The container registry storing container images

    Incorrect. Argo CD doesn't manage container registries.

  2. B The Git server hosting the manifests

    Incorrect. While Argo CD reads from Git, it doesn't host the Git server; that's separate infrastructure.

  3. C The reconciliation engine that implements the continuous feedback loop to enforce desired state

    Correct. Argo CD is the GitOps controller/reconciliation engine that continuously watches Git and reconciles the cluster to match.

  4. D The CI system building and testing code

    Incorrect. Argo CD is not a CI system; it's a CD/GitOps tool used after CI produces artifacts.

GitOps Terminology

Q2. In GitOps, what is meant by the 'control plane' managing the 'data plane'?

Reveal answer and explanations
  1. A The Kubernetes control plane manages application workloads

    Incorrect. This reverses the relationship—control plane manages workloads in the data plane.

  2. B Operators manually command changes to cluster state

    Incorrect. Manual commands violate GitOps principles.

  3. C The GitOps controller continuously compares state and issues corrective actions to bring the live system into compliance

    Correct. In GitOps, the 'control plane' is the reconciliation engine reading desired state; the 'data plane' is the live system being reconciled.

  4. D The API server controls Kubelet processes

    Incorrect. That's standard Kubernetes architecture, not the GitOps pattern.

  5. E CI/CD pipelines trigger changes in the runtime environment

    Incorrect. CI/CD and GitOps are separate concerns.

GitOps Terminology

Q3. What does 'continuous' reconciliation explicitly guarantee in a GitOps system?

Reveal answer and explanations
  1. A That the system will never experience downtime

    Incorrect. No system guarantees zero downtime; continuous reconciliation reduces drift, not downtime overall.

  2. B That if actual state drifts from desired state, the system will detect and correct this drift without human intervention

    Correct. Continuous reconciliation means the system permanently works to align actual with desired state, maintaining convergence automatically.

  3. C That all developer commits are automatically merged and deployed

    Incorrect. Automatic merging bypasses important controls; continuous reconciliation works on merged/approved changes.

  4. D That every change reaches production within 5 minutes of being committed

    Incorrect. While GitOps often has fast deployment, 'continuous reconciliation' doesn't define a specific RTO/RPO.

GitOps Terminology

Q4. What makes Git's immutable commit history critical to GitOps state stores (as opposed to other versioned systems)?

Reveal answer and explanations
  1. A Commits provide cryptographic proof of who made changes and when, creating an audit trail that cannot be retroactively altered

    Correct. Git's SHA-1 hashes and commit chain make history tamper-evident and audit-safe, which is essential for compliance and reliability.

  2. B Git's distributed nature means every clone is a backup

    Incorrect. Redundancy is beneficial but not the core reason for GitOps adoption.

  3. C Git is the only system that supports branches

    Incorrect. Other systems support versioning and branching.

  4. D Git compresses storage more efficiently than databases

    Incorrect. Storage efficiency is not a GitOps requirement.

  5. E Immutable commits prevent accidental overwrites during merge conflicts

    Incorrect. Merge conflict handling doesn't depend on immutability.

GitOps Terminology

Q5. In GitOps systems, 'desired state' is best defined as:

Reveal answer and explanations
  1. A The current running state of applications in the cluster

    Incorrect. Current running state is actual state, not desired state—a key distinction in GitOps.

  2. B The intended configuration of the entire system expressed declaratively and stored in version control

    Correct. Desired state is the authoritative specification of how the system should be configured, maintained in a version-controlled repository.

  3. C The state that the system should be in after the next CI pipeline execution

    Incorrect. CI output is different from desired state; desired state includes post-deployment configuration.

  4. D The backup state kept for disaster recovery purposes

    Incorrect. Backup/DR state is separate from the desired state that drives continuous reconciliation.

Drill GitOps Terminology with the full bankDomain Drill mode targets your weak areas — paid feature

How this domain is tested

GitOps Terminology accounts for 20% of the CGOA exam. Expect questions that test recall of terminology and the ability to read short scenarios — not deep configuration. Use the sample questions above as difficulty calibration; if any feel hard, the rest of our 24-question domain bank will close those gaps.