
CGOA (Certified GitOps Associate) is the Linux Foundation and CNCF's beginner certification for GitOps, the practice of running infrastructure and applications from declarative files in Git that an automated agent keeps applied to the system. It is concept-focused and tool-neutral: the four OpenGitOps principles, the terms (desired state, drift, reconciliation), how GitOps relates to IaC and CI/CD, deployment patterns, and tools such as Argo CD and Flux. It is a good first certificate for freshers heading into DevOps and a short step before the more hands-on Argo CAPA.
This guide follows the official Linux Foundation exam page: the five domains with weights, the principles and terms explained simply, push vs pull, a 2-week plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Level | Beginner; no prerequisites |
| Price | US$250 exam only; US$495 with an annual training subscription |
| Validity | 2 years |
| Eligibility | 12 months to schedule and take the exam; two attempts (one retake) |
Read the official CGOA exam page and the OpenGitOps principles, which the exam's terminology follows.
Domains and weights
| Domain | Weight | Topics (from the Linux Foundation) |
|---|---|---|
| GitOps Principles | 30% | Declarative; versioned and immutable; pulled automatically; continuously reconciled |
| GitOps Terminology | 20% | Continuous; declarative description; desired state; state drift; state reconciliation; GitOps-managed software system; state store; feedback loop; rollback |
| GitOps Patterns | 20% | Deployment and release patterns; progressive delivery; pull vs event-driven; architecture patterns (in-cluster and external reconcilers, state store management) |
| Related Practices | 16% | Configuration as code; infrastructure as code; DevOps and DevSecOps; CI and CD |
| Tooling | 14% | Manifest formats and packaging; state stores (Git and alternatives); reconciliation engines (Argo CD, Flux and others); notifications, observability and CI integration |
The four principles in plain words
| Principle | Meaning | Example |
|---|---|---|
| Declarative | Describe what the system should look like, not the steps to get there | A Kubernetes Deployment YAML saying "3 replicas of image v2" |
| Versioned and immutable | Desired state is stored with full history; changes are new versions, not edits in place | Every change is a Git commit you can review and revert |
| Pulled automatically | Agents fetch the desired state from the store themselves | Argo CD or Flux inside the cluster polls the repo |
| Continuously reconciled | Agents keep comparing actual state with desired state and fix differences | A manual kubectl edit is reverted to what Git says |
Key terms
- Desired state: the configuration in the state store. Actual state: what is running.
- Drift: any difference between them. Reconciliation: the agent's work to remove drift.
- State store: where desired state lives; usually Git, but OCI registries and buckets also work.
- Feedback loop: sync status, health and alerts flowing back to the team (for example, a Slack message when a sync fails).
- Rollback: revert the commit; the agent applies the previous state.
Push-based CI/CD vs pull-based GitOps
| Push (classic pipeline) | Pull (GitOps) |
|---|---|
| The CI server runs kubectl or helm against the cluster | An agent in or near the cluster pulls from Git and applies |
| CI needs cluster credentials | Cluster credentials stay inside the cluster |
| Drift after deployment goes unnoticed | Drift is detected and corrected continuously |
| History lives in pipeline logs | History is the Git log |
In a typical setup, CI still builds and tests the image, then commits the new image tag to a config repository; the GitOps agent deploys it. Webhooks can trigger the agent immediately (event-driven) instead of waiting for the next poll.
2-week study plan
| Days | Focus | Practice |
|---|---|---|
| 1–4 | Principles and terminology; read the OpenGitOps documents twice | Explain each term in one sentence from memory |
| 5–8 | Related practices (IaC, CaC, CI/CD, DevSecOps); patterns: environments as folders or branches, app-of-apps, progressive delivery, in-cluster vs external reconciler | Draw a repo layout for dev, staging and prod |
| 9–12 | Tooling: Helm, Kustomize, Argo CD, Flux, notifications | Install Argo CD or Flux on kind; deploy from your own repo; cause drift and watch it heal |
| 13–14 | Review and practice questions | Book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. Name the four OpenGitOps principles.
Declarative; versioned and immutable; pulled automatically; continuously reconciled.
2. What is drift?
A difference between the desired state in the store and the actual state of the system.
3. Someone scales a deployment by hand from 3 to 5 replicas. What does a GitOps agent with self-healing do?
Detects drift and sets it back to 3, as declared in Git.
4. How do you roll back a bad release in GitOps?
Revert the commit in the state store; the agent applies the previous version.
5. Why is pull-based deployment considered more secure than push?
The CI system doesn't need credentials to the cluster; only the in-cluster agent does.
6. Is Git the only allowed state store?
No. Any versioned, immutable store works, such as an OCI registry or object storage, though Git is most common.
7. Name two reconciliation engines.
Argo CD and Flux.
8. Which principle is broken if a script runs a series of imperative commands to configure servers?
Declarative.
9. Where does CI usually fit in a GitOps workflow?
It builds, tests and publishes the image, then updates the image tag in the config repo.
10. Name two ways to package Kubernetes manifests.
Helm charts and Kustomize overlays (plain YAML also works).
11. What is progressive delivery?
Releasing gradually (canary, blue-green, feature flags) with automated checks before full rollout.
12. What is the difference between pull and event-driven reconciliation?
Pull polls the store on an interval; event-driven reacts to a webhook or event straight away.
13. What is the feedback loop in GitOps?
Sync status, health and alerts reported back to people and tools.
14. How is IaC related to GitOps?
IaC provides declarative definitions; GitOps adds versioned storage plus automated pull and reconciliation.
15. Where should secrets go in a GitOps repo?
Never in plain text. Use encrypted secrets (for example Sealed Secrets or SOPS) or references to an external secret manager.
After CGOA
- Go hands-on with the Argo CAPA and GH-200 GitHub Actions.
- Learn it on our GitOps and GitHub Actions course and DevOps course.
- See live jobs for freshers.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches multi-cloud DevOps, Kubernetes and GitOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the CGOA exam?
The Linux Foundation and CNCF Certified GitOps Associate: a beginner online, proctored, multiple-choice exam on GitOps principles, patterns and tooling.
How long is the CGOA exam?
90 minutes.
Which CGOA domain has the most weight?
GitOps Principles at 30%.
What are the four GitOps principles?
Declarative; versioned and immutable; pulled automatically; continuously reconciled.
Does CGOA have prerequisites?
No. There are no prerequisites.
CGOA or CAPA first?
CGOA covers concepts and is tool-neutral; CAPA goes deeper into the Argo tools. Many people take CGOA first.



