CGOA and CAPA are complementary, not duplicates
CGOA is vendor-neutral. It asks why GitOps works: declarative desired state, immutable version history, automatic pull, continuous reconciliation, feedback, promotion, architecture, packaging, state stores, and interoperability. Argo CD and Flux are examples, not the center of the credential.
CAPA goes deeper into the Argo ecosystem. It covers Argo Workflows, Argo CD, Argo Rollouts, and Argo Events. Start with CGOA when the conceptual operating model is weak; add the CAPA roadmap when product-specific execution depth is needed.
Exact 50-question allocation
10 questions: desired state, actual state, drift, reconciliation, state store, feedback, rollback.
15 questions: declarative, versioned and immutable, pulled automatically, continuously reconciled.
8 questions: CaC, IaC, DevOps, DevSecOps, CI, CD, policy and supply chain.
10 questions: promotion, release, progressive delivery, events, reconciler and repository architecture.
7 questions: formats, packaging, state stores, engines, notifications, observability, CI handoff.
Phase 1 — Build the terminology model
Study window: Week 1. Learn to describe a managed system without product names first.
- Separate desired state, actual state, state drift, reconciliation, convergence, health, and operation status.
- Explain why a Git repository alone is not a GitOps system.
- Identify the state store and its immutability, history, access, and recovery requirements.
- Trace feedback from repository revision to attempted revision, applied revision, health, and error.
- Practice rollback as a desired-state change, with emergency live-change procedures as a controlled exception.
- Complete questions 1-10 and the terminology flashcards.
Phase 2 — Prove the four OpenGitOps principles
Study window: Week 2. Convert each principle into observable evidence.
- Replace imperative-only deployment procedures with declarative target state.
- Protect revisions, retain complete history, and pin immutable artifact identities.
- Explain automatic pull without claiming polling is the only trigger mechanism.
- Use periodic reconciliation to recover from missed event notifications.
- Demonstrate drift correction, suspension, legitimate field ownership, and controller conflict.
- Complete questions 11-25 and project 1.
Phase 3 — Connect related practices
Study window: Week 3. Map GitOps onto a larger engineering system without treating adjacent practices as synonyms.
- Compare Configuration as Code and Infrastructure as Code with the GitOps operating model.
- Separate CI artifact creation from CD environment authorization.
- Promote one immutable digest rather than rebuilding per environment.
- Add DevSecOps controls: state-store protection, policy as code, secret encryption or external retrieval, artifact trust, and least privilege.
- Use review-time tests and runtime policy as complementary controls.
- Complete questions 26-33 and project 2.
Phase 4 — Practice patterns and architecture
Study window: Week 4. Reason about tradeoffs rather than memorizing one repository layout.
- Separate deployment from release and compare canary with blue-green delivery.
- Define bounded success, failure, and inconclusive behavior for progressive delivery.
- Compare periodic pull with event-driven acceleration and require idempotence.
- Compare in-cluster and external reconcilers by identity, connectivity, tenancy, scale, and failure domain.
- Choose monorepo or multirepo boundaries from ownership and blast radius.
- Complete questions 34-43 and begin project 3.
Phase 5 — Tooling, interoperability, and final simulation
Study window: Week 5. Make tool choices serve the principles.
- Render Helm, Kustomize, or other formats deterministically with pinned dependencies.
- Compare Git with any proposed alternative state store against required properties.
- Explain reconciliation-engine duties and limits using Argo CD, Flux, or alternatives.
- Monitor source readiness, desired/attempted/applied revisions, drift, duration, errors, health, suspension, and notifications.
- Finish project 3, review all 40 cards, and take 50 questions within 90 minutes.
- For Argo depth after CGOA, continue to the CAPA roadmap.
Three portfolio projects
Declarative state, protected history, pull, drift, feedback, rollback, failures, and teardown.
Open projectsCI/CD boundaries, one immutable artifact, policy, secrets, staged promotion, and recovery.
Open projectsIn-cluster and external agents, event acceleration, packaging, canary evidence, and observability.
Open projectsAll learning surfaces
Exact 10/15/8/10/7 allocation.40 unique cards
Principles, patterns, and tooling recall.3 schema-complete projects
Architecture, failures, security, cost, and cleanup.CGOA study guide
Connected technical explanation and exam strategy.Complementary CAPA path
Deepen Argo product skills.Editorial policy
Sourcing, originality, and corrections.
Official references
Current format, duration, product details, domains, and competencies.
Open official product pagePublic CGOA repository outline; compare it with the product page because the displayed domains differ.
Open CGOA curriculumCanonical four-principle model and glossary.
Open OpenGitOpsLinux Foundation candidate policies and delivery requirements.
Open handbookCommon LF multiple-choice exam rules; verify appointment details.
Open MC FAQFrequently asked questions
Is CGOA active in 2026?
Yes. As verified August 21, 2026, the Linux Foundation advertises Certified GitOps Associate as an active beginner-level, online, proctored multiple-choice certification.
What is the CGOA exam format?
The product page states 90 minutes and multiple choice. Linux Foundation common multiple-choice rules currently describe 60 questions. Appointment and delivery rules can change, so verify the official product page, candidate handbook, MC FAQ, and appointment confirmation.
Which domain weights does this course use?
Exactly the currently advertised product-page blueprint: GitOps Terminology 20% (10 of 50), GitOps Principles 30% (15), Related Practices 16% (8), GitOps Patterns 20% (10), and Tooling 14% (7).
Why does the curriculum repository show a different outline?
The linked CNCF repository currently displays GitOps Fundamentals, Principles & Practices, Tooling & Implementation, and Security & Observability at 25% each. The product page displays the five-domain blueprint used here. This is documented as an inconsistency only; no transition is asserted.
Should CGOA candidates study Argo CD or Flux?
Study them as implementations of vendor-neutral concepts: state stores, rendering, pull, reconciliation, drift, health, notifications, and CI handoff. Do not reduce CGOA to product commands. For dedicated Argo ecosystem depth, study CAPA next.
Are the practice materials exam dumps?
No. All 50 questions, 40 flashcards, and three labs are original and based on public official documentation. They do not reproduce confidential, recalled, leaked, copied, or live exam items.
Start the vendor-neutral path
Take the exact weighted bank, explain every distractor, drill the cards, and prove the principles through three disposable labs.
Start questionsReview cardsBuild projectsRead guide