Home › Roadmaps › Certified Argo Project Associate
Active CNCF / Linux Foundation certification

Certified Argo Project Associate (CAPA) Roadmap

A five-phase route through the Argo ecosystem: orchestrate jobs with Argo Workflows, reconcile Kubernetes applications with Argo CD, control release exposure with Argo Rollouts, and connect event dependencies to safe triggers with Argo Events.

90 minutesOnline proctored MCBeginner18 + 17 + 9 + 6 questions40 cards · 3 labs
Current blueprint: Verified August 21, 2026 against the official Linux Foundation product page. This course allocates exactly 50 original practice questions as Argo Workflows 36% = 18, Argo CD 34% = 17, Argo Rollouts 18% = 9, and Argo Events 12% = 6. Always recheck the official page and appointment details before testing.

CAPA adds product depth after vendor-neutral GitOps

CAPA is Argo-specific. Candidates must know when each Argo project fits, the resources it introduces, and how controllers interact with Kubernetes, repositories, artifacts, traffic, metrics, and events.

CGOA is vendor-neutral. It teaches desired state, reconciliation, the OpenGitOps principles, related practices, architecture patterns, and interoperable tooling. Use the CGOA roadmap first when the conceptual model is weak; use CAPA to turn that model into Argo ecosystem depth.

Exact 50-question allocation

Argo Workflows · 36%

18 questions: fundamentals, artifacts, templates, spec, steps, DAGs, data processing, parameters, retries, and RBAC.

ARGO CD · 34%

17 questions: applications, sync, refresh, health, automated sync, Helm, Kustomize, AppProjects, hooks, waves, and drift.

Argo Rollouts · 18%

9 questions: Rollout, blue-green, canary, traffic routing, AnalysisTemplate, AnalysisRun, and uncertainty.

Argo Events · 12%

6 questions: EventSource, EventBus, Sensor, Trigger, filtering, RBAC, authentication, and idempotence.

Phase 1 — Map the four Argo products

Study window: Days 1-3. Build the product-selection model before memorizing YAML.

  • Use Argo Workflows for container-native job and data-pipeline orchestration.
  • Use Argo CD to compare and synchronize Kubernetes desired and live state.
  • Use Argo Rollouts for blue-green, canary, traffic shaping, and metric analysis.
  • Use Argo Events to receive events, transport them, evaluate dependencies, and invoke triggers.
  • Draw an integrated flow without claiming every installation needs all four projects.
  • Review the complete CAPA guide product comparison.

Phase 2 — Master Argo Workflows

Study window: Week 1-2. This is the largest domain and should receive the most hands-on time.

  • Explain Workflow as both definition and execution state, then use WorkflowTemplate for reuse.
  • Read entrypoint, templates, arguments, inputs, outputs, parameters, and artifact paths.
  • Compare steps groups with DAG dependencies and enhanced depends logic.
  • Pass small values as parameters and files or directories as artifacts through a configured repository.
  • Use workflow UID in artifact keys; configure retention, garbage collection, and scoped credentials.
  • Add bounded retry, timeout, exit handler, parallelism, synchronization, and least-privilege ServiceAccount.
  • Complete questions 1-18 and project 1.

Phase 3 — Master Argo CD

Study window: Week 3. Separate comparison, operation, and health dimensions.

  • Define Application source, target revision, path or chart, destination, project, and sync policy.
  • Distinguish target state, live state, sync status, refresh, sync operation status, and health.
  • Render Helm charts and Kustomize overlays deterministically with pinned inputs.
  • Constrain source repositories, destinations, and resource kinds with AppProject plus Kubernetes RBAC.
  • Test manual sync, automated sync, self-heal, prune, allow-empty safety, retry, and rollback strategy.
  • Order an idempotent migration and smoke test with hooks and sync waves.
  • Complete questions 19-35 and project 2.

Phase 4 — Control release exposure with Argo Rollouts

Study window: Week 4. Move beyond Deployment readiness into evidence-driven delivery.

  • Explain how Rollout uses a Pod template and manages ReplicaSets.
  • Build blue-green active and preview Services and understand manual versus automatic promotion.
  • Build canary setWeight and pause steps; distinguish replica weighting from traffic routing.
  • Use an ingress, service mesh, Gateway API, or plugin only when fine-grained traffic control is required.
  • Define reusable AnalysisTemplate metrics and observe AnalysisRun executions.
  • Set bounded success, failure, error, and inconclusive behavior before rollout.
  • Complete questions 36-44 and the Rollouts portion of project 3.

Phase 5 — Connect Argo Events and simulate the exam

Study window: Week 5. Treat event delivery as retried, duplicated, and potentially hostile input.

  • Trace EventSource → EventBus → Sensor dependency → Trigger.
  • Authenticate webhook or broker sources, filter context and data, and allowlist mapped parameters.
  • Give the Sensor ServiceAccount only permission to invoke approved trigger resources.
  • Use event IDs for idempotence or deduplication and retain status and metrics.
  • Complete questions 45-50 and the integrated project 3 failure matrix.
  • Review all 40 cards and complete the exact 50-question bank inside 90 minutes.

Three portfolio projects

Reliable Workflows pipeline

DAG, steps, templates, artifacts, parameters, retries, RBAC, telemetry, and GC.

Open projects
Argo CD operations lab

AppProject, Helm, Kustomize, sync, drift, prune, hooks, waves, health, and recovery.

Open projects
Event-driven progressive delivery

Events, Workflows, reviewed Git intent, Rollouts analysis, idempotence, and end-to-end failure injection.

Open projects

All learning surfaces

50 original CAPA questions
Exact 18/17/9/6 allocation.40 unique cards
Cross-product terminology and behavior.3 substantial projects
Architecture, steps, failures, security, costs, and cleanup.CAPA study guide
Technical model and exam strategy.Complementary CGOA path
Vendor-neutral GitOps principles and patterns.Editorial policy
Sourcing and exam integrity.

Official references

Linux Foundation CAPA page

Current format, duration, level, domains, competencies, registration, and resources.

Open official product page
CNCF CAPA curriculum

Public curriculum repository for the credential.

Open CAPA curriculum
Argo Workflows

Workflow concepts, templates, artifacts, DAGs, and operations.

Open Workflows docs
Argo CD

Application concepts, sources, synchronization, reconciliation, and health.

Open Argo CD docs
Argo Rollouts

Blue-green, canary, traffic management, and analysis.

Open Rollouts docs
Argo Events

EventSource, EventBus, Sensor, Trigger, filters, and security.

Open Events docs

Frequently asked questions

Is CAPA active in 2026?

Yes. As verified August 21, 2026, the Linux Foundation advertises CAPA as an active online proctored multiple-choice certification at beginner experience level.

How long is CAPA?

The current product page lists a 90-minute multiple-choice exam. Read the candidate handbook, multiple-choice instructions, and appointment confirmation for current delivery rules.

What are the current product-page domain weights?

Argo Workflows 36%, Argo CD 34%, Argo Rollouts 18%, and Argo Events 12%. This course maps those percentages to exactly 18, 17, 9, and 6 questions.

Should I learn every Argo project equally?

No. Allocate study by the current blueprint. Workflows and Argo CD together represent 70%, but Rollouts and Events still contribute 30% and are essential to understanding the full ecosystem.

How is CAPA different from CGOA?

CAPA requires deeper Argo product behavior: Workflow specs, Applications, sync, Rollouts, analysis, and event architecture. CGOA stays vendor-neutral and emphasizes GitOps principles, terminology, adjacent practices, patterns, and tool roles.

Are these live or recalled exam questions?

No. The 50 questions, 40 cards, and three projects are original educational content based on public official documentation. They do not use dumps, copied banks, recollections, leaks, or live exam material.

Independent study resource: PrepKloud is not affiliated with or endorsed by the Linux Foundation, CNCF, or the Argo project. Marks belong to their owners. Official objectives, product versions, policies, pricing, and attempts can change. Verify primary sources. Use only disposable authorized systems and synthetic data. A practice result, lab, or certification does not prove production readiness or guarantee employment.

Start the Argo ecosystem path

Take the exact weighted bank, then build Workflows, Argo CD, Rollouts, and Events behavior in safe integrated labs.

Start questionsReview cardsBuild projectsRead guide