CGOA exam prep: why 50 clusters of Argo CD got me an 82

I wrote the longer version, with the full domain breakdown and my prep timeline, on my blog.

I run Argo CD in production on 50 Kubernetes clusters across several public clouds. Before studying for the Certified GitOps Associate, I took a practice test cold and scored 82. Passing is 75, so fine on paper. The questions I missed were the ones I didn't expect to miss.

The CGOA does not grade how well you run Argo CD. It grades whether you can apply the OpenGitOps specification word for word.

Format

60 multiple-choice questions, 90 minutes, 75 to pass. No terminal, no kubectl, no YAML. Argo CD and Flux appear as examples, never as the thing being graded.

Tooling is roughly one question in seven. In my experience it gets most of people's prep time anyway, because sync options and CRDs are what we touch every day.

30% of the exam is four sentences

About 18 questions come from the four OpenGitOps principles:

1. Declarative. The system is described declaratively.
2. Versioned and Immutable. Desired state is stored in a way that enforces immutability and versioning, and retains a complete version history.
3. Pulled Automatically. Software agents automatically pull the desired state declarations from the source.
4. Continuously Reconciled. Software agents continuously observe actual system state and attempt to apply the desired state.

Memorize the exact wording. The options are written so a paraphrase lands you on the wrong one. "Pulled Automatically" is the usual slip: people read it as "applied automatically", but the agent pulls and the CI pipeline does not push.

Terminology cost me the most

Terminology is 20%, and the spec vocabulary sits in the question stem too, so a fuzzy term means you misread the question before you see the options.

Learn desired state, actual state, state drift, state store, reconciliation, feedback loop, rollback, and "continuous" (recurring, not instantaneous). The pair people mix up most: Git is the state store, the cluster holds the actual state.

My 82 came from here. I'd fixed plenty of state drift. I was sloppy about the exact definition.

Pull vs push, and related practices

In the pull model an agent inside the cluster watches Git and applies changes, so CI holds no cluster credentials. In the push model a runner calls kubectl apply or Helm. That deploys fine, and it isn't GitOps.

The wrong answer on a patterns question is usually a pipeline that deploys everything correctly. A couple caught me because I was thinking about implementation. Also know that a reconciler can run in-cluster or externally as long as it pulls, that the merge is the promotion, and that reverting the commit is the rollback.

Related Practices (16%) is mostly review with a DevOps background: Infrastructure as Code, Configuration as Code, DevSecOps, CI vs CD. In GitOps, CI builds and tests, the reconciler deploys. A few CI/CD split questions made me stop, and I'm not sure whether that section has shifted since I sat it. If you're preparing in late 2026, check the current curriculum first.

How I'd prepare

I spent about 8 hours over a weekend. Aimed right from the start, I think 5 or less.

1. Read the OpenGitOps principles and the GitOps glossary. About 20 minutes. Say the principles out loud without looking.
2. Take the free LFS169 Introduction to GitOps course. Around 4 hours, and it follows the exam domains in order.
3. Do practice questions until the wrong answers look obviously wrong. For this step I built a free CGOA practice test from the concepts I had to reason through after that 82, so you can see which domain is weak before exam day.

I wasted about 2 hours on Flux and Argo CD docs. Nobody cares about argocd app sync flags here. More study links are in awesome-kubestronaut.

The mental model

GitOps clicked when I saw it as a control loop rather than a deployment tool. Same pattern as a Kubernetes controller: watch desired state, compare to actual, reconcile. Desired state lives in Git instead of etcd.

The four principles then map onto the loop: how you express desired state, how you store it, how the agent gets it, what the agent does with it.

98 out of 100, first attempt. The concepts aren't hard; they need precision, which is probably why people with years of Argo CD keep landing around 80 first try.

I still don't know whether those Related Practices questions were bad luck or the curriculum drifting. If you sit it after me, tell me which.

Originally published on yetmike.com