
CAPA (Certified Argo Project Associate) is the Linux Foundation and CNCF certification for the four Argo projects that many Kubernetes platform teams use: Argo CD for GitOps deployments, Argo Workflows for container-native pipelines and data jobs, Argo Rollouts for canary and blue-green releases, and Argo Events for event-driven automation. GitOps with Argo CD now appears in many DevOps job descriptions in Hyderabad and Bengaluru, so this is a useful second certificate after a Kubernetes one.
This guide follows the official Linux Foundation exam page: the four domains with weights, what each Argo project does, manifests you should recognise, a 4-week lab plan and 15 original practice questions.
Quick facts (Linux Foundation, November 2026)
| Item | Detail |
|---|---|
| Format | Online, proctored, multiple choice |
| Duration | 90 minutes |
| Prerequisites | None |
| Price | US$250 exam only; US$299 with the LFS256 Argo course; US$495 with an annual training subscription |
| Validity | 2 years |
| Eligibility | 12 months to schedule and take the exam; one retake included |
Read the official CAPA exam page before booking.
Domains and weights
| Domain | Weight | Objectives (from the Linux Foundation) |
|---|---|---|
| Argo Workflows | 36% | Fundamentals; generating and consuming artifacts; workflow templates; the workflow spec; DAGs; data processing jobs |
| Argo CD | 34% | Fundamentals; synchronising applications; the Application resource; Helm and Kustomize; common reconciliation patterns |
| Argo Rollouts | 18% | Fundamentals; common progressive rollout strategies; AnalysisTemplate and AnalysisRun |
| Argo Events | 12% | Fundamentals; components and architecture |
The four projects in one table
| Project | What it does | Key resources |
|---|---|---|
| Argo CD | Keeps the cluster in sync with manifests in Git (GitOps); shows drift; syncs manually or automatically | Application, AppProject, ApplicationSet |
| Argo Workflows | Runs multi-step jobs where each step is a container; steps or DAG dependencies; artifacts passed between steps | Workflow, WorkflowTemplate, ClusterWorkflowTemplate, CronWorkflow |
| Argo Rollouts | Replaces a Deployment with canary or blue-green releases, traffic shifting and automated analysis | Rollout, AnalysisTemplate, AnalysisRun |
| Argo Events | Listens for events (webhooks, Git pushes, queues, schedules) and triggers actions such as workflows | EventSource, EventBus, Sensor |
Manifests to recognise
# Argo CD Application with automated sync, pruning and self-heal
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: shop
namespace: argocd
spec:
project: default
source:
repoURL: https://github.com/example/shop-config.git
targetRevision: main
path: overlays/prod # Kustomize overlay
destination:
server: https://kubernetes.default.svc
namespace: shop
syncPolicy:
automated: { prune: true, selfHeal: true }
# Argo Rollouts canary: 20% → pause → 50% → full
apiVersion: argoproj.io/v1alpha1
kind: Rollout
metadata: { name: cart }
spec:
replicas: 5
strategy:
canary:
steps:
- setWeight: 20
- pause: { duration: 5m }
- setWeight: 50
- pause: {} # wait for manual promotion
selector: { matchLabels: { app: cart } }
template: { metadata: { labels: { app: cart } }, spec: { containers: [ { name: cart, image: example/cart:2.1 } ] } }
# Argo Workflows DAG: B and C run in parallel after A, D after both
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata: { generateName: etl- }
spec:
entrypoint: main
templates:
- name: main
dag:
tasks:
- { name: A, template: step }
- { name: B, template: step, dependencies: [A] }
- { name: C, template: step, dependencies: [A] }
- { name: D, template: step, dependencies: [B, C] }
- name: step
container: { image: alpine:3.20, command: [echo, "done"] }
4-week lab plan
| Week | Focus | Lab (kind or minikube) |
|---|---|---|
| 1 | Argo CD: Applications, sync, health, drift, Helm and Kustomize sources, ApplicationSets | Deploy an app from your own Git repo; change Git and watch it sync |
| 2 | Argo Workflows: steps vs DAG, templates, parameters, artifacts, CronWorkflows | Build a three-step data workflow that passes an artifact |
| 3 | Argo Rollouts: canary and blue-green, pauses, promotion, abort, AnalysisTemplates | Run a canary that aborts automatically when an analysis fails |
| 4 | Argo Events: EventSource, EventBus, Sensor; review all four; mocks | Trigger a workflow from a webhook; book the exam |
15 practice questions with answers
These are original questions written for this guide, not exam questions.
1. In GitOps, what is the source of truth for what runs in the cluster?
The Git repository.
2. Someone edits a Deployment directly with kubectl. What does Argo CD report, and what does selfHeal do?
The app shows OutOfSync (drift); selfHeal reverts it to match Git.
3. What does prune: true do in an Argo CD sync policy?
Deletes cluster resources that were removed from Git.
4. Which Argo CD resource generates many Applications, for example one per cluster?
ApplicationSet.
5. Which Argo CD resource restricts which repos and destinations a team may use?
AppProject.
6. In Argo Workflows, what is each step run as?
A container in a pod.
7. Steps B and C must run in parallel after A. Which template type expresses this most clearly?
A DAG with dependencies.
8. How do you reuse a workflow definition across many workflows?
A WorkflowTemplate (or ClusterWorkflowTemplate for the whole cluster).
9. A report must run every night at 2 AM. Which resource?
CronWorkflow.
10. How does one workflow step pass a file to the next?
Output and input artifacts, stored in an artifact repository such as S3 or MinIO.
11. Which Argo Rollouts strategy runs the new version alongside the old one and switches all traffic at once after checks?
Blue-green.
12. What decides automatically whether a canary should continue or roll back?
An AnalysisRun created from an AnalysisTemplate (for example, a Prometheus error-rate query).
13. A canary step has pause: {} with no duration. What happens?
It waits indefinitely until someone promotes the rollout.
14. In Argo Events, which component listens to external sources such as webhooks?
The EventSource.
15. Which Argo Events component decides what to trigger when events arrive?
The Sensor (events travel between them on the EventBus).
After CAPA
- Learn GitOps hands-on in our GitOps and GitHub Actions course and Kubernetes course.
- Pair it with CKAD, GH-200 and the Prometheus PCA (Rollouts analysis often uses Prometheus).
- See live DevOps and platform jobs.
Cloud Soft Solutions in Ameerpet, Hyderabad teaches multi-cloud DevOps, Kubernetes and GitOps with real-time projects. See the APEX program and all courses.
📞 Call +91 96660 19191 · WhatsApp · Flat No. 513, 5th Floor, Nilagiri Block, Aditya Enclave, Ameerpet, Hyderabad
Frequently Asked Questions
What is the CAPA exam?
The Linux Foundation and CNCF Certified Argo Project Associate: an online, proctored, multiple-choice exam on Argo CD, Argo Workflows, Argo Rollouts and Argo Events.
How long is the CAPA exam?
90 minutes.
Which CAPA domain has the most weight?
Argo Workflows at 36%, followed by Argo CD at 34%.
Does CAPA have prerequisites?
No. There are no prerequisites, but Kubernetes basics help a lot.
How long is CAPA valid?
2 years.
What is Argo CD used for?
GitOps: keeping a Kubernetes cluster in sync with manifests stored in Git.



