20 Free CAPA Sample Questions with Answers

How to use these CAPA practice questions

Work through the 20 CAPA sample questions in one sitting without looking anything up. For each question, decide on an answer first, then open the answer and read the explanation, including when you were right, because a correct guess and a correct line of reasoning look identical until the exam rewords the question. Mark every question as right, wrong or guessed, and count a guess as wrong when you score yourself. Give the set about 30 minutes, which is the average time per question on the real exam multiplied by twenty. The aim is to find out which exam domains are already solid and which ones need study before you buy the exam.

The official exam format is 60 questions in 90 minutes, with a passing score of 75%, according to the Linux Foundation documentation checked on 2026-10-23.

With JavaScript enabled, each answer starts collapsed behind a Show answer button so you can test yourself. Without JavaScript, and for any crawler or screen reader that reads the raw page, every answer and explanation is already visible below its question.

These questions were written for GoldenKube practice. They are not copied from the real exam, and nothing on this page tells you what the real exam will ask.

• Read the question twice and underline the constraint words: "most", "least", "first", "only", "not".
• Eliminate options you can prove wrong before you pick between the rest.
• Where a question says to select all that apply, every correct option must be chosen and none of the wrong ones.
• Read the explanation even for questions you got right; it often names the nearby concept the exam likes to swap in.

Argo Workflows (7 questions)

dag:
  tasks:
  - name: A
    template: process
  - name: B
    dependencies: [A]
    template: analyze

inputs:
  artifacts:
  - name: data
    path: /tmp/data
    s3:
      bucket: my-bucket
      key: data.csv

ARGO CD (7 questions)

spec:
  ignoreDifferences:
    - group: apps
      kind: Deployment
      jsonPointers:
        - /spec/replicas

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

Argo Rollouts (4 questions)

Argo Events (2 questions)

Score yourself

The Linux Foundation lists a passing score of 75% for CAPA. On a set of 20 questions that is 15 correct. Reaching 15 here is a useful signal and not a prediction: 20 questions is a small sample, and the real exam covers every domain in its published weights. Use the table below to decide what to do next. Count only the questions you answered correctly without help, and be strict about it: a question you got right for the wrong reason belongs in the missed pile. Then repeat the exercise a few days later with a different set from the full bank so that you are measuring understanding and not memory of these specific questions.

Count your misses per domain, using the headings above. One missed question in a domain is noise; three misses in one domain is a study plan. The practice mode on GoldenKube does this sorting for you by sending you back to the domains where you are weakest.

Argo Workflows: what it tests

Argo Workflows is the largest CAPA domain. Expect the Workflow custom resource and its templates, the difference between steps and DAG layouts, parameters and artifacts for passing data, reusable WorkflowTemplates and cluster-wide variants, scheduled runs with CronWorkflow, retry and failure handling, and how a workflow runs as Pods. Questions give a requirement and ask which template type or feature satisfies it. A frequent trap is choosing steps when dependencies between tasks are the point, which is what a DAG expresses, or confusing a parameter, which is a small value, with an artifact, which is a file or object. Read each requirement for ordering, data passing and reuse, because those three words point to different features.

Write a three-task workflow twice, once as steps and once as a DAG, and note what changes. That exercise explains most layout questions.

Argo CD: what it tests

Argo CD is the second largest CAPA domain and covers declarative continuous delivery for Kubernetes. Expect the Application resource with its source and destination, sync status and health status, manual and automated sync with options such as pruning and self-healing, projects for grouping and restricting applications, ApplicationSets for generating many applications, and the app-of-apps pattern. Questions ask how Argo CD decides a state or what a policy does. The common trap is mixing sync status, which compares Git with the cluster, and health status, which describes whether the resources are working. An application can be out of sync yet healthy, and the exam likes that case.

Create a small table of sync status values against health status values and describe a realistic situation for each cell. It makes the two ideas permanently distinct.

Argo Rollouts: what it tests

Argo Rollouts covers progressive delivery for Kubernetes. Expect the Rollout resource as a replacement for a Deployment, the blue-green and canary strategies, steps that shift traffic gradually, analysis that checks metrics to decide whether to continue, and how traffic management integrations work. Questions describe a release risk and ask which strategy or feature fits. A frequent trap is thinking a canary needs a service mesh: a basic canary can be done by adjusting replica counts, while precise percentage control of traffic needs a traffic router. Knowing what each level of control requires answers most questions. Read the stated risk first, then pick the strategy that addresses it with the least extra machinery.

Describe in two sentences what happens during a canary and what happens during a blue-green release, including how a failure is detected. Those descriptions are the answers.

Argo Events: what it tests

Argo Events covers event-driven automation. Expect event sources that listen to systems such as webhooks, message queues and calendars, the event bus that carries events, sensors that define dependencies and conditions, and triggers that start actions such as launching a workflow. Questions ask which resource plays which part of the flow. The trap is confusing the sensor with the event source: the source detects and publishes an event, while the sensor subscribes, applies conditions and fires a trigger. The domain is small, so a single clear picture of the flow from source to trigger is enough preparation. Remember that a sensor can wait for several events before it fires, which is a favourite scenario in questions about this project.

Sketch a flow where a webhook starts a workflow, labelling the event source, event bus, sensor and trigger. Then change the example to a schedule and relabel it.

What a 20-question CAPA sample can and cannot tell you

A set of 20 questions is a screening test, not a measurement. With only a few questions per domain, one lucky guess or one unlucky wording moves your result by five percentage points, and a domain with only two questions behind it says almost nothing about that domain's true strength. The set is also fixed, so after one read-through it measures your memory of these items and not your command of CAPA. Use it to choose where to start studying, not to decide whether you are ready, and then rely on the larger bank, where questions repeat only after a gap and the app tracks which domains stay weak.

A second limit is style. Written practice questions share one author voice, while a real exam draws on many writers and reads differently. Treat any practice score, here or elsewhere, as one input next to the official curriculum, hands-on experience with the technology, and the documentation of the project itself.

A one-week plan after the CAPA sample set

After the sample set, spend a week turning the result into a plan. Start with the domains where you missed questions and read the matching part of the official curriculum before you try more questions, because practice is far more useful once you can explain the topic. Return to practice in short daily sessions, review every missed question the next day, and leave the last day for a fresh mixed set. Keep a simple note of which concepts caused misses; the same three or four ideas usually explain most of them, and naming them is what turns practice into progress.

The largest CAPA domain is Argo Workflows, at 36% of the published weights. If two domains tie for weakest in your tally, start with the heavier one, and keep the other 3 domains ticking over with short reviews.

Adjust the pace to your calendar. If you have more time, spread the same steps over two or three weeks and add a second mixed session at the end of each week. If you have less, keep days 1 to 3 and day 6 and accept a rougher picture. What matters is that every study session starts from a specific weak domain and ends with a check, not that the plan is followed to the letter.

Practice the full CAPA bank

These 20 questions are a small slice of the GoldenKube CAPA bank, which holds 40 questions. In practice mode the app serves the questions you are due to review first, then the domain where you are weakest, and it brings missed questions back after a gap until you answer them correctly. You can answer 10 questions as a guest without an account; after that a free account keeps your progress, and no credit card is asked for at any point. Each answer comes with the same kind of written explanation you saw on this page, so a wrong answer is always followed by the reasoning that fixes it.

Practice mode shows one question at a time and gives the verdict and explanation as soon as you answer. A focus option lets you stay inside a single domain until it feels solid, which is the natural next step after finding your weakest domain on this page. There is no timer and no exam simulation in practice mode; the goal is learning, not performance under pressure.

Frequently asked questions