Browse Linux Foundation and CNCF Guides

CGOA Study Plan

May 23, 2026

CGOA study plan for GitOps terminology, principles, related practices, patterns, tooling, and final review.

On this page

This plan prepares Certified GitOps Associate (CGOA) as a 90-minute multiple-choice exam. It assumes you understand basic DevOps or Kubernetes vocabulary and need a focused route through GitOps reasoning.

Seven-day route

Day Focus What to do
Day 1 Scope and terminology Read the root guide and memorize desired state, drift, reconciliation, state store, managed system, feedback loop, and rollback.
Day 2 GitOps principles Study declarative state, versioned and immutable records, pull-based automation, and continuous reconciliation.
Day 3 Related practices Separate Configuration as Code, Infrastructure as Code, DevOps, DevSecOps, CI, and CD.
Day 4 Patterns Review deployment/release patterns, progressive delivery, pull vs event-driven, and in-cluster vs external reconciler choices.
Day 5 Tooling Review manifest formats, packaging, state stores, reconcilers such as Argo CD and Flux, notifications, and observability.
Day 6 Mixed scenarios Use the cheat sheet to drill drift, rollback, CI/CD, compliance, and tool-fit traps.
Day 7 Final check Re-read domain weights, verify official Linux Foundation details, and review every missed scenario as principle violated or preserved.

If you only have 48 hours

  1. Read the cheat sheet and memorize the four GitOps principles.
  2. Drill terminology until you can explain drift, reconciliation, state store, and feedback without notes.
  3. Spend the second block on pattern traps: CI vs CD, push vs pull, canary vs rollback, manual patch vs versioned state.
  4. Verify the current Linux Foundation CGOA page before scheduling.

Readiness signals

  • You can explain why a manual production patch creates drift unless desired state is updated.
  • You can distinguish CI artifact creation from GitOps CD reconciliation.
  • You can choose between pull-based sync and event-driven triggers without treating them as opposites.
  • You can identify the feedback signal that proves sync, drift, health, or rollback.
  • You can map a tooling question to state store, packaging, reconciler, notification, and observability.
Revised on Monday, June 15, 2026
Cheat Sheet
FAQ