Linux Foundation CGOA exam guide for GitOps principles, reconciliation, state drift, CI/CD, and tooling decisions.
This guide covers the Certified GitOps Associate (CGOA) credential from the Linux Foundation. CGOA is a strong niche page because it is focused, vendor-recognized, and maps cleanly to real platform-engineering work: desired state, Git as a state store, reconciliation, drift, deployment patterns, and GitOps tooling.
The exam is a multiple-choice GitOps certification. It is not a hands-on Kubernetes terminal exam like CKA or CKAD, but Kubernetes and cloud-native delivery context still help.
| Item | Guide value |
|---|---|
| Vendor | Linux Foundation / CNCF ecosystem |
| Credential | Certified GitOps Associate |
| Code or shorthand | CGOA |
| Exam style | Online proctored, multiple choice |
| Study level | Beginner GitOps and platform delivery |
| Best fit | DevOps, platform, SRE, and CI/CD practitioners who need GitOps vocabulary and decision logic |
| Official domain | Weight | What to master |
|---|---|---|
| GitOps Terminology | 20% | Desired state, state drift, reconciliation, state store, feedback loop, rollback. |
| GitOps Principles | 30% | Declarative, versioned and immutable, pulled automatically, continuously reconciled. |
| Related Practices | 16% | Configuration as Code, Infrastructure as Code, DevOps, DevSecOps, CI, and CD. |
| GitOps Patterns | 20% | Deployment and release patterns, progressive delivery, pull vs event-driven, architecture patterns. |
| Tooling | 14% | Manifest formats, packaging, state stores, reconcilers such as Argo CD and Flux, notifications and observability. |
Read each CGOA scenario as a state-management question. The strongest answer usually preserves a declarative desired state, keeps change history versioned, lets a reconciler pull and compare state, and uses feedback to detect drift.
| Stem clue | Better answer | Weak answer |
|---|---|---|
| desired state differs from live state | reconcile from the state store | manually patch production and forget Git |
| rollback is required | revert or promote a versioned state change | re-create resources from memory |
| continuous delivery is discussed | separate CI artifact build from CD reconciliation | let CI mutate the cluster directly without state history |
| manifest packaging is mentioned | choose a tool-aware format and lifecycle | treat YAML files as unmanaged text dumps |
| security is mentioned | review, sign, restrict, and audit changes to state | give the reconciler broad untracked privileges |
Use the current Linux Foundation CGOA page for live price, duration, retake, language, and domain details.