← CAPA hub

Free CAPA Sample Questions

10 CAPA questions with full explanations for every option, free to view on this page.

Argo Workflows

Q1. In a DAG template, what does the `dependencies` field express?

Reveal answer and explanations
  1. A The container images that must already exist in the registry.

    Incorrect. Container image availability is not modeled with DAG dependencies.

  2. B The Kubernetes namespaces where the workflow may run.

    Incorrect. Namespace placement is not what `dependencies` expresses.

  3. C Which tasks must complete before another task is eligible to run.

    Correct. `dependencies` defines prerequisite tasks for DAG scheduling.

  4. D Which Argo CD projects can deploy the workflow.

    Incorrect. Argo CD project authorization is unrelated to Workflow DAG dependencies.

  5. E Configure Argo CD automated sync to recreate the Workflow whenever the source repository changes, then treat sync status as the task execution result.

    Incorrect. Argo CD can apply Workflow manifests, but the Workflow controller owns task execution and workflow status.

Argo Workflows

Q2. Which statement best describes memoization in Argo Workflows?

Reveal answer and explanations
  1. A It can reuse previous template outputs when the configured cache key matches.

    Correct. Memoization can skip repeated work by reusing cached outputs for matching inputs.

  2. B It automatically promotes a blue-green deployment after a preview test.

    Incorrect. Blue-green promotion belongs to Argo Rollouts.

  3. C It prevents Argo CD from comparing live resources against desired state.

    Incorrect. Argo CD comparison is not controlled by Workflow memoization.

  4. D It turns a webhook payload into a Sensor trigger parameter.

    Incorrect. Event payload parameterization is handled by Argo Events Sensors.

  5. E Use Argo Rollouts traffic routing to split execution between workflow pods until the desired task has completed successfully.

    Incorrect. Rollouts controls application delivery traffic and does not schedule or coordinate workflow task execution.

Argo Workflows

Q3. What is the main responsibility of the workflow controller?

Reveal answer and explanations
  1. A To serve Git repositories to Argo CD Applications.

    Incorrect. Repository serving and manifest generation are Argo CD repo-server responsibilities.

  2. B To watch `Workflow` resources and create or manage the Kubernetes pods needed to execute them.

    Correct. The workflow controller reconciles `Workflow` resources into executable pods and workflow status.

  3. C To shift production traffic between stable and canary services.

    Incorrect. Traffic shifting is handled by Argo Rollouts integrations.

  4. D To translate Sensor dependencies into CloudEvents.

    Incorrect. Sensor event processing belongs to Argo Events.

  5. E Use Argo Rollouts traffic routing to split execution between workflow pods until the desired task has completed successfully.

    Incorrect. Rollouts controls application delivery traffic and does not schedule or coordinate workflow task execution.

Argo Workflows

Q4. A user can create `Workflow` resources but their workflow pods fail to create `ConfigMap` objects. What is the most likely issue?

Reveal answer and explanations
  1. A The workflow is missing an Argo CD sync wave annotation.

    Incorrect. Sync wave annotations do not grant runtime Kubernetes permissions.

  2. B The Rollout controller is not installed.

    Incorrect. The Rollouts controller is not required for Workflow resource templates.

  3. C The EventBus has no JetStream persistence.

    Incorrect. EventBus persistence does not affect workflow pod RBAC.

  4. D The workflow service account lacks RBAC permissions for the resource action.

    Correct. Workflow pods use a service account, and resource templates need that account to have the required Kubernetes permissions.

  5. E Configure Argo CD automated sync to recreate the Workflow whenever the source repository changes, then treat sync status as the task execution result.

    Incorrect. Argo CD can apply Workflow manifests, but the Workflow controller owns task execution and workflow status.

Argo Workflows

Q5. Which command is commonly used to submit a workflow manifest from the Argo CLI?

Reveal answer and explanations
  1. A `argo submit`

    Correct. `argo submit` creates a workflow run from a manifest or template.

  2. B `argocd app sync`

    Incorrect. `argocd app sync` synchronizes an Argo CD Application.

  3. C `kubectl argo rollouts promote`

    Incorrect. `kubectl argo rollouts promote` advances a Rollout, not a workflow.

  4. D `argo-events run`

    Incorrect. Argo Events does not use `argo-events run` as the normal workflow submission command.

Argo Workflows

Q6. Why is it risky to put a secret value directly into a workflow parameter in Git?

Reveal answer and explanations
  1. A Parameters are always converted into Rollout analysis metrics.

    Incorrect. Workflow parameters are not converted into Rollout metrics.

  2. B Argo CD will delete the workflow when it sees a parameter.

    Incorrect. Argo CD does not delete resources merely because parameters exist.

  3. C The secret may be exposed in Git history, workflow specs, status, logs, or UI surfaces.

    Correct. Sensitive values should use Kubernetes secrets or supported secret-injection patterns rather than plain parameters.

  4. D Workflow parameters cannot contain strings.

    Incorrect. Parameters commonly contain strings.

  5. E Use Argo Rollouts traffic routing to split execution between workflow pods until the desired task has completed successfully.

    Incorrect. Rollouts controls application delivery traffic and does not schedule or coordinate workflow task execution.

Argo Workflows

Q7. Why is `serviceAccountName` important in a workflow spec?

Reveal answer and explanations
  1. A It chooses which Git repository Argo CD will clone for the workflow.

    Incorrect. Git repository selection is not controlled by `serviceAccountName`.

  2. B It configures the external load balancer used by a Rollout.

    Incorrect. Rollout traffic routing is unrelated to workflow service accounts.

  3. C It stores the default artifact repository credentials directly in the `Workflow` status.

    Incorrect. Credentials should not be stored directly in workflow status.

  4. D It determines the Kubernetes identity and RBAC permissions used by workflow pods.

    Correct. Workflow pods run as the configured service account and receive its Kubernetes permissions.

Argo Workflows

Q8. A Workflow succeeds, but its final notification step should still know whether earlier steps failed or passed. Which mechanism is designed for final status-aware handling?

Reveal answer and explanations
  1. A A Rollout post-promotion analysis.

    Incorrect. Rollout post-promotion analysis is unrelated to workflow final notifications.

  2. B An `onExit` handler using workflow status variables.

    Correct. Exit handlers can inspect workflow status variables and send final notifications or cleanup actions.

  3. C An ApplicationSet matrix generator.

    Incorrect. ApplicationSet generators create Applications, not workflow final handlers.

  4. D An EventBus stream filter.

    Incorrect. EventBus stream filtering is not a workflow exit mechanism.

  5. E Configure Argo CD automated sync to recreate the Workflow whenever the source repository changes, then treat sync status as the task execution result.

    Incorrect. Argo CD can apply Workflow manifests, but the Workflow controller owns task execution and workflow status.

Argo Workflows

Q9. What does a resource template allow a workflow to do?

Reveal answer and explanations
  1. A Change an Argo CD Application's destination cluster without syncing it.

    Incorrect. Application destination changes are Argo CD concerns.

  2. B Define Prometheus metrics used by a canary analysis.

    Incorrect. Canary metrics are modeled through Rollouts analysis resources.

  3. C Create, patch, delete, or wait on Kubernetes resources as part of the workflow.

    Correct. Resource templates let workflows perform Kubernetes resource actions during execution.

  4. D Attach an external event dependency to a Sensor.

    Incorrect. Event dependencies belong to Argo Events Sensors.

  5. E Use Argo Rollouts traffic routing to split execution between workflow pods until the desired task has completed successfully.

    Incorrect. Rollouts controls application delivery traffic and does not schedule or coordinate workflow task execution.

Argo Workflows

Q10. A platform team wants every submitted workflow in a namespace to inherit default pod metadata and limits unless overridden. Which configuration concept is relevant?

Reveal answer and explanations
  1. A `workflowDefaults`

    Correct. Workflow defaults can provide common default spec values for workflows handled by the controller.

  2. B `syncWindows`

    Incorrect. Sync windows are Argo CD scheduling controls.

  3. C `trafficRouting`

    Incorrect. Traffic routing belongs to Rollouts.

  4. D `eventDependency`

    Incorrect. Event dependencies belong to Argo Events Sensors.

  5. E Use Argo Rollouts traffic routing to split execution between workflow pods until the desired task has completed successfully.

    Incorrect. Rollouts controls application delivery traffic and does not schedule or coordinate workflow task execution.

Take the full timed CAPA mock90 minutes · 60 questions · free with account

About these questions

These questions are written against the current CAPA curriculum — not scraped exam dumps. The full CAPA library here has 120 questions; the broader platform covers the rest of the Golden Kubestronaut path.