CAPA practice test

CAPA exam snapshot

Exam facts from the Linux Foundation pages, checked 2026-10-28; full table with sources on the CAPA certification page.

What this CAPA practice test is

This page starts a free CAPA practice session on GoldenKube. The official CAPA exam is 60 questions in 90 minutes with a passing score of 75%, as read from the Linux Foundation documentation on 2026-10-28. The GoldenKube CAPA bank held 40 questions when this page was written; the live count is shown above. One question at a time. As soon as you answer you see whether you were right and read the explanation; reloading the page keeps the verdict on screen. The next question comes from the questions due for review first, then from the domain where you are weakest and still have unseen questions, then from the rest of the bank. Use it as a check across all four Argo projects, one project per session, with the project documentation open next to it.

Every CAPA question in the bank has a written explanation, so a wrong answer is always followed by the reasoning that fixes it.

What the CAPA bank covers

The CAPA bank is the smallest on the site and follows the official weights closely: Argo Workflows and Argo CD hold most of the questions, then Argo Rollouts and Argo Events. The table compares the official domain weights, checked against the CAPA certification page on 2026-10-28, with the share of the bank each domain holds and the number of explained questions, both read from the database when the page is served. Argo Workflows is the heaviest domain at 36%, so it deserves the largest share of your study time whatever the bank's share is.

All 40 questions have a written explanation. Live from the database; the CAPA bank coverage report explains the method.

A domain whose bank share is well below its weight is one to study from the official curriculum and the project documentation as well; the bank-coverage report linked below tracks these gaps over time.

How the bank covers the CAPA curriculum

CAPA covers four separate projects, and the CNCF curriculum weights them very unevenly: Argo Workflows 36%, Argo CD 34%, Argo Rollouts 18% and Argo Events 12%. The GoldenKube CAPA bank is the smallest on the site, 40 questions, and follows the same order: 14 each for Workflows and Argo CD, 7 for Rollouts and 5 for Events. The shares are close to the weights, but the absolute numbers are small, so the bank is a vocabulary check across all four projects rather than a deep drill of any one of them. Argo Workflows has six curriculum topics, more than any other CAPA domain, and deserves the most reading in its documentation. Every question maps to one official domain. Counts are taken from the seed bank at build time; the topic names are quoted from the curriculum PDF.

1. Argo Workflows

   36% of the exam · 14 questions in the bank

   How a Workflow is specified, how templates and DAGs are composed and how artifacts move between steps.

   Official curriculum topics

   • Understand Argo Workflow Fundamentals
   • Generating and Consuming Artifacts
   • Understand Argo Workflow Templates
   • Understand the Argo Workflow Spec
   • Work with DAG (Directed-Acyclic Graphs)
   • Run Data Processing Jobs with Argo Workflows

2. ARGO CD

   34% of the exam · 14 questions in the bank

   How Argo CD compares Git with the cluster, syncs applications, renders Helm and Kustomize and reconciles drift.

   Official curriculum topics

   • Understand Argo CD Fundamentals
   • Synchronize Applications Using Argo CD
   • Use Argo CD Application
   • Configure Argo CD with Helm and Kustomize
   • Identify Common Reconciliation Patterns

3. Argo Rollouts

   18% of the exam · 7 questions in the bank

   How a Rollout replaces a Deployment for canary and blue-green releases and how analysis decides to continue or abort.

   Official curriculum topics

   • Understand Argo Rollouts Fundamentals
   • Use Common Progressive Rollout Strategies
   • Describe Analysis Template and AnalysisRun

4. Argo Events

   12% of the exam · 5 questions in the bank

   What the Argo Events components are and how an event travels from a source to a trigger.

   Official curriculum topics

   • Understand Argo Events Fundamentals
   • Understand Argo Event Components and Architecture

Weights from the official certification page; question counts from the GoldenKube bank when this page was built; topics as named in the CNCF curriculum PDF listed under Sources.

Try three CAPA questions

Three questions from the bank with their answers and explanations. The CAPA sample-questions page has twenty more; the practice session has the whole bank.

spec:
  syncPolicy:
    automated:
      prune: true
      selfHeal: true

How to practise CAPA with GoldenKube

CAPA asks about four projects that share a name but solve different problems, so the loop is organised by project and pairs every practice session with the matching documentation. The 40-question bank is quick to finish; its value lies in the explanations and in the review ladder, which brings back each miss after 12 other answers, then after 1 day and after 4 days, until three correct answers in a row mark it mastered. Use Focus mode to stay inside one project per session, because mixing Workflows templates with Argo CD Applications in one sitting is exactly the confusion the exam exploits. Bookmark any question where you were unsure which project a field belongs to. The mock exam can only draw the 40 questions the bank holds, fewer than the official 60, so use it as a timed check of all four projects together rather than a rehearsal of exam length.

With a bank this size every question repeats by the second week, so a rising score partly reflects memory. The documentation reading on days 3 to 10 is what prepares you for the questions the bank does not contain.

Common CAPA mistakes

CAPA options frequently describe a real feature with the wrong default, or a real field in the wrong project. The eight pitfalls below are stated as the Argo CD, Argo Rollouts, Argo Workflows and Argo Events documentation states them, with a link to each page. Most of them are defaults, which are cheap to memorise and costly to guess.

1. 1. Treating Synced and Healthy as the same thing

   Sync status says whether the live state matches the target state in Git; health says whether the application is running correctly. Health has its own values (Healthy, Progressing, Degraded, Suspended, Missing, Unknown), so an app can be Synced and Degraded at once.

   Source: Argo CD docs: Core concepts

2. 2. Assuming automated sync prunes and self-heals

   As a safety mechanism, automated sync does not delete resources removed from Git unless prune is enabled, and changes made directly to the live cluster do not trigger a sync unless selfHeal is enabled.

   Source: Argo CD docs: Automated sync policy

3. 3. Getting sync wave order backwards

   Waves are set with the argocd.argoproj.io/sync-wave annotation. Argo CD applies the lowest number first; resources and hooks default to wave 0, and a negative wave runs before them.

   Source: Argo CD docs: Sync phases and waves

4. 4. Handing out the app of apps repository

   App of apps is one Argo CD Application that consists only of other Applications. The docs call it an admin-only tool, because creating Applications in arbitrary Projects is an admin-level capability.

   Source: Argo CD docs: Cluster bootstrapping (app of apps)

5. 5. Expecting a pause step to time out on its own

   A canary pause step without a duration pauses the Rollout indefinitely until it is promoted, for example with kubectl argo rollouts promote. Without traffic management, setWeight is approximated by replica counts.

   Source: Argo Rollouts docs: Canary strategy

6. 6. Misreading an inconclusive analysis

   An AnalysisRun ends Successful, Failed or Inconclusive, and the Rollout update continues, aborts or pauses respectively. An AnalysisTemplate is the reusable spec; the AnalysisRun is its instantiation.

   Source: Argo Rollouts docs: Analysis and progressive delivery

7. 7. Confusing a template with a WorkflowTemplate

   A template (lower case) is a task inside a Workflow, of type container, script, dag, steps, resource or suspend. A WorkflowTemplate is a definition of a Workflow that lives in the cluster; the docs call the naming collision unfortunate.

   Source: Argo Workflows docs: Workflow templates

8. 8. Leaving the EventBus out of the Argo Events path

   EventSources publish events to the EventBus and Sensors subscribe to it to execute triggers. The EventBus implementations are NATS (deprecated), Jetstream and Kafka.

   Source: Argo Events docs: EventBus

Mock exam

The official CAPA exam has 60 questions, but the bank holds 40, and a mock never repeats a question, so the CAPA mock exam uses all 40 with the official 90 minutes and the 75% threshold. That leaves more time per question than the real exam: it checks every domain under a clock, not pacing or stamina, and the result is practice feedback. Mock exams need a free account; your history of runs is kept on the exam's mock page.

Frequently asked questions

Sources

• Certified Argo Project Associate (official certification page) (read 2026-10-28)
• CNCF curriculum: CAPA Curriculum (PDF) (read 2026-10-28)
• Argo CD docs: Resource health (read 2026-10-28)
• Argo CD docs: FAQ (polling interval) (read 2026-10-28)
• Argo Workflows docs: Core concepts (read 2026-10-28)
• Argo Events docs: Architecture (read 2026-10-28)
• Argo Events docs: Sensor (read 2026-10-28)
• Argo CD docs: Core concepts (read 2026-10-28)
• Argo CD docs: Automated sync policy (read 2026-10-28)
• Argo CD docs: Sync phases and waves (read 2026-10-28)
• Argo CD docs: Cluster bootstrapping (app of apps) (read 2026-10-28)
• Argo Rollouts docs: Canary strategy (read 2026-10-28)
• Argo Rollouts docs: Analysis and progressive delivery (read 2026-10-28)
• Argo Workflows docs: Workflow templates (read 2026-10-28)
• Argo Events docs: EventBus (read 2026-10-28)