Linux Foundation / CNCF CAPA: Certified Argo Project Associate (CAPA)

Last checked November 10, 2026 against the official Linux Foundation / CNCF exam page.

1. Question 1Argo Workflows

   A platform engineer submits a Workflow manifest, but the run fails immediately because the controller cannot find the template it was told to start with. Which field should the engineer check first?

   1. Ametadata.labels, which must include a tag that matches the controller version
   2. Bspec.arguments, which must contain at least one parameter with a default value
   3. Cspec.serviceAccountName, which must point to a service account with cluster-admin rights
   4. Dspec.entrypoint, which must match the name of a template defined under spec.templates
   Show answer and explanationHide answer

   Correct answer: D

   spec.entrypoint names the template where a run begins, so it must match a template name in spec.templates. Labels, arguments and the service account do not decide which template starts, and cluster-admin rights are not a fix for a missing entrypoint.

2. Question 2Argo CD

   Which statement best describes how Argo CD applies the GitOps model?

   1. AIt builds container images from source code and pushes them to a registry after each commit
   2. BIt replaces the Kubernetes scheduler and decides which node runs each pod in the cluster
   3. CIt stores application secrets in encrypted form inside the cluster's etcd database for later use
   4. DIt treats a Git repository as the source of truth and keeps comparing live cluster state with the desired state stored there
   Show answer and explanationHide answer

   Correct answer: D

   GitOps keeps the desired state in Git, and Argo CD continuously compares the live cluster against it. Building images, scheduling pods and storing secrets are handled by other tools or components, so those options are not the GitOps model.

3. Question 3Argo Rollouts

   A team wants canary and blue-green releases with automated analysis for an application that currently runs as a Deployment. Which Argo Rollouts resource would they change to achieve this?

   1. AA Service, which gains weighted traffic splitting across ReplicaSets by default
   2. BA StatefulSet, which keeps a stable network identity for each canary pod
   3. CA Rollout, which replaces the Deployment and adds canary and blue-green strategies
   4. DA HorizontalPodAutoscaler, which adjusts replica counts based on canary metrics
   Show answer and explanationHide answer

   Correct answer: C

   A Rollout is the Argo Rollouts workload that takes the place of a Deployment and adds the canary and blue-green strategies with analysis. A Service only routes traffic, while a StatefulSet and an HPA serve different purposes.

4. Question 4Argo Events

   In Argo Events, what is the job of a Sensor?

   1. AIt receives events from external systems such as webhooks and buckets and publishes them to the bus
   2. BIt keeps a long-term audit log of every event so that past deliveries can be queried later
   3. CIt waits for dependency events and, when its conditions are met, runs triggers such as a Workflow
   4. DIt runs the messaging cluster that carries events between the other Argo Events components
   Show answer and explanationHide answer

   Correct answer: C

   A Sensor declares event dependencies and runs its triggers, such as creating a Workflow, once the dependencies are satisfied. Receiving external events is the job of an EventSource, and the messaging layer is the EventBus.

5. Question 5Argo Workflows

   In Argo Workflows, what does a step that uses a container template become when the workflow runs?

   1. AA long-running Deployment that keeps the container alive between runs
   2. BA ConfigMap that stores the container output for later steps
   3. CA CronJob that starts the container on a fixed schedule
   4. DA Kubernetes pod that runs the container image for that step
   Show answer and explanationHide answer

   Correct answer: D

   Each container-based node in a workflow runs as a pod created for that step. A Deployment is meant for long-running services, a CronJob is a separate scheduled resource, and a ConfigMap cannot run code.