Certifications guide

CAPA: The Certified Argo Project Associate Exam, Domain by Domain

CAPA is a 90-minute, multiple-choice exam across four Argo projects — and the biggest domain is not the one people expect. If you booked it because you use Argo CD daily, the weighting is the first thing to look at.

read: 7 min read; read
last updated: August 2026; last updated

Overview

What CAPA actually certifies

The Certified Argo Project Associate is the CNCF and Linux Foundation credential for the Argo project family. It is an online, proctored, multiple-choice exam of 90 minutes, priced at $250 for the exam alone, with no prerequisites, one free retake, a 12-month eligibility window and a certification valid for two years. Neither a question count nor a pass mark is published.

Four domains, one per project: Argo Workflows 36 %, Argo CD 34 %, Argo Rollouts 18 % and Argo Events 12 %. Read the first two again — Workflows is the largest domain on the paper, slightly ahead of Argo CD, and the two projects have almost nothing in common beyond a name and a controller pattern.

All four domains now have cards. Gnoseed's GitOps track covers Argo CD in depth and carries a dedicated Argo Rollouts module — together 52 % of the exam — and the separate Argo Workflows & Argo Events track covers the other 48 %. Two tracks rather than one is deliberate: a DAG engine and an event router are a different subject from continuous delivery, and folding them into the GitOps deck would have made both worse. Gnoseed is not affiliated with CNCF or the Linux Foundation and neither sells nor proctors this exam; verify every figure against the official exam page before you book.

Breakdown

The exam at a glance

One exam, four independent projects, and a weighting that surprises most Argo CD users.

CAPA

Certified Argo Project Associate

AssociateMultiple choice · online proctored · 90 min · $250Prereq: None

Argo Workflows (36 %) covers workflow fundamentals, generating and consuming artifacts, workflow templates, the workflow spec, DAGs and running data-processing jobs. Argo CD (34 %) covers fundamentals, synchronising applications, the Application resource, configuring Helm and Kustomize sources, and common reconciliation patterns. Argo Rollouts (18 %) covers fundamentals, the common progressive rollout strategies, and AnalysisTemplate and AnalysisRun. Argo Events (12 %) covers fundamentals plus the event components and their architecture.

Choose this if…

You run Argo CD and want the rest of the family named and understood
Your platform already uses Workflows for batch or CI-style jobs
You want a multiple-choice CNCF exam that is tool-specific rather than conceptual

Study with Gnoseed

GitOps with Argo CD & Flux · 140 cards Argo Workflows & Argo Events · 90 cards Kubernetes Fundamentals · 91 cards

The mistake to avoid

This is not an Argo CD exam with extras

Argo is a family of four separate projects that happen to share a name and a home at the CNCF. Argo CD reconciles clusters to declared state, Argo Rollouts runs progressive deployments, Argo Workflows is a container-native workflow engine for DAGs and batch jobs, and Argo Events wires event sources to triggers. Knowing one of them well tells you very little about the other three.

The blueprint reflects that. Argo CD is only about a third of the exam, and it is the least deep third — its competencies stop at fundamentals, syncing, the Application resource, Helm and Kustomize sources and reconciliation patterns. There is nothing there about repo-server internals or ApplicationSet generator types. Meanwhile Argo Workflows, at 36 %, asks about the workflow spec itself: templates, artifacts in and out, DAG dependencies and running real data-processing jobs.

If you are an Argo CD user with no Workflows experience, plan your time by that gap rather than by comfort. The Argo CD domain is where you will already score; the marks you do not have are in the project you have never installed.

What this deck covers

Argo CD and Rollouts, which is 52 % of the paper

The GitOps track maps onto the Argo CD domain closely: Argo CD Core for fundamentals and the Application resource, Sync Strategies for synchronising applications — manual and automated policies, prune, self-heal, sync waves and hooks — Repo & App Patterns for Helm, Kustomize and directory sources, and Practical Tips for the reconciliation patterns as they actually go wrong: Synced but Degraded, an app that will not prune, a rollback that does not stick.

The Argo Rollouts module was written for this exam's third domain and stays on the mechanics the blueprint names: the Rollout resource and its relationship to ReplicaSets, workloadRef, canary steps such as setWeight and setCanaryScale, blue-green fields including activeService, previewService, autoPromotionEnabled and scaleDownDelaySeconds, AnalysisTemplate versus ClusterAnalysisTemplate, the Successful, Failed and Inconclusive results an AnalysisRun can return, and the kubectl argo rollouts commands you would use at a manual gate.

The vendor-neutral half of the same track is useful here too: the Delivery & Architecture Patterns module explains what canary, blue-green and analysis-gated promotion mean before Rollouts implements them, which is the layer the exam's "understand fundamentals" competencies sit at.

The other 48 %

Argo Workflows and Argo Events, in their own track

The Argo Workflows & Argo Events deck was written against these two domains. Its modules line up with what the blueprint names: Workflow Fundamentals for the Workflow resource, entrypoint, the template types and the controller, server and Pod anatomy; The Workflow Spec for parameters, conditionals, retry strategies, exit handlers and lifecycle hooks; Templates & Reuse for WorkflowTemplate, ClusterWorkflowTemplate, CronWorkflow, memoization and synchronization; Artifacts for producing, consuming and garbage-collecting them; and DAGs & Data Processing for dependencies, enhanced depends logic and fan-out with withItems, withParam and withSequence.

For Argo Events the blueprint is narrower — fundamentals plus components and architecture — and a single module covers it: EventSource and the CloudEvents normalisation, the EventBus and its NATS Streaming, JetStream and Kafka implementations, Sensor dependencies addressed by eventSourceName and eventName, trigger types and operations, conditions, the five filter types and trigger parameterization. Twelve per cent is small and the architecture is one diagram's worth of concepts, so it is the cheapest block of marks on the paper.

What flashcards do not buy you here. The Workflows domain asks about the spec, and the spec is something you learn by writing. Cards will hold the field names, defaults and the difference between an invocator and a template type; they will not give you the feel of debugging a DAG that stalled. Run a handful of workflows against a real cluster alongside the deck.

CAPA or CGOA

One certifies tools, the other certifies the practice

The two are easy to confuse and test opposite things. CGOA is vendor-neutral: half of it is the OpenGitOps principles and glossary, and every reconciliation engine in existence shares a single 14 % domain. CAPA is the mirror image — entirely about specific tools, with no vendor-neutral theory domain at all, and it includes two projects that have nothing to do with GitOps.

Neither is a prerequisite for the other and both are 90-minute, $250, multiple-choice papers. Pick by what you are trying to prove: that you understand the delivery model, or that you can operate the Argo stack. If you want both, taking CGOA first makes the Argo CD domain here feel like revision, because the reconciliation patterns are the same ideas with product names attached.

Logistics

Cost, retakes and whether it is worth it

CAPA is $250 for the exam alone, with one retake, a 12-month eligibility window and two years of validity. Bundles with the matching course cost more; confirm the current price at the source.

Is it worth it? It is worth it in proportion to how much of the Argo project you actually run. Because Argo Workflows carries a larger share of the blueprint than Argo CD, teams that use only Argo CD tend to find the exam broader than the job — which is either wasted effort or a useful push into batch and event-driven work, depending on where your platform is heading. Decide which before you pay.

FAQ

Common questions

What are the CAPA exam domains and their weights? +

Four domains, one per project: Argo Workflows 36 %, Argo CD 34 %, Argo Rollouts 18 % and Argo Events 12 %. Workflows being the largest domain is the detail most candidates miss.

Is the CAPA exam hands-on? +

No. It is an online, proctored, multiple-choice exam of 90 minutes with no terminal. The content is practical — the Workflows domain asks about the spec itself — but the format is a knowledge paper.

Do I need to know Argo Workflows if I only use Argo CD? +

Yes. Argo Workflows is 36 % of the exam, more than Argo CD, and Argo Events adds another 12 %. Nearly half the paper is on projects an Argo CD user may never have installed, so budget your study time there.

Does Gnoseed cover the whole CAPA blueprint? +

Yes, across two tracks. The GitOps track covers the Argo CD domain in depth and has a dedicated Argo Rollouts module, which is 52 % of the exam. The Argo Workflows and Argo Events track covers the remaining 48 %. They are separate decks because a workflow engine and an event router are a different subject from continuous delivery.

How much does CAPA cost and how long is it valid? +

The exam alone is $250 and includes one free retake, with a 12-month window in which to sit it. The certification is valid for two years. Check the official page for current pricing before booking.

Should I take CAPA or CGOA? +

CGOA certifies GitOps as a vendor-neutral practice — principles, terminology and patterns. CAPA certifies the Argo tool family, including two projects that are not about GitOps at all. Neither requires the other; pick the one that matches what you want to prove.

Does CAPA cover Flux? +

No. CAPA is scoped to the Argo projects. If you want a credential that treats Argo CD and Flux as interchangeable implementations of the same idea, that is CGOA, where reconciliation engines share one 14 % domain.

Start with the domain you have never installed

Plant your first seed today. Ten minutes a day across both tracks covers all four domains — and the marks you do not have yet are in Workflows.

Start learning free