Certified Argo Project Associate (CAPA)
Demonstrate proficiency in GitOps delivery and automation using the Argo Project ecosystem: Argo CD for declarative GitOps continuous delivery, Argo Workflows for container-native pipelines, Argo Rollouts for advanced progressive delivery, and Argo Events for event-driven orchestration.
Official Exam Specification & Quick Facts
Question Difficulty Breakdown
Exam Guidelines & Simulation Rules
Frequently Asked Questions (FAQ)
The CAPA is a multiple-choice certification from the CNCF and Linux Foundation validating foundational and intermediate skills across the four core Argo projects: Argo CD, Argo Workflows, Argo Rollouts, and Argo Events.
The CAPA is a 90-minute multiple-choice examination consisting of 60 questions administered online with remote proctoring.
A passing scaled score of 75% is required. Results are displayed immediately upon submission.
Domains include: (1) Argo CD (38%), (2) Argo Workflows (24%), (3) Argo Rollouts (22%), and (4) Argo Events (16%).
An Application is a CRD binding a target Git repository and path to a target Kubernetes cluster and namespace. An AppProject provides a logical boundary restricting allowed source repositories, target destinations, and cluster-scoped resource permissions for teams.
Manual requires operator intervention to sync. Automated sync reconciles differences automatically, optionally supporting prune (deleting orphaned resources) and selfHeal (reverting out-of-band manual cluster changes).
Sync waves order resource creation using integer annotations (e.g. argocd.argoproj.io/sync-wave: '-1'). Resource hooks execute auxiliary tasks at specific phases (PreSync, Sync, PostSync, SyncFail), such as running database migrations.
Argo Rollouts replaces the standard Kubernetes Deployment with a Rollout CRD, managing progressive traffic shifting via service meshes, automated metric analysis (AnalysisRuns), and instant rollbacks upon failure.
An AnalysisRun queries metric providers (Prometheus, Datadog, CloudWatch) during rollouts to verify error rate and latency thresholds before progressing canary steps.
Argo Workflows defines parallel and sequential containerized pipelines using Directed Acyclic Graphs (DAGs) or steps, supporting parameter passing, artifacts (S3/GCS), retries, and exit handlers.
Argo Events uses EventSources (capturing webhooks, SQS, Kafka), an EventBus (NATS messaging backbone), and Sensors (filtering and transforming events) to trigger Triggers (e.g. creating Argo Workflows or K8s resources).
DevOps engineers, cloud platform architects, SREs, and developers responsible for automated GitOps continuous deployment and containerized pipeline automation.