← CAPA hub

CAPA — Argo Workflows

36% of the CAPA exam. Sample questions below; the full library has 44 questions tagged to this domain.

Sample questions on Argo Workflows

Argo Workflows

Q1. Why is an artifact repository configured for Argo Workflows?

Reveal answer and explanations
  1. A To store workflow input and output artifacts outside the pods that produce them.

    Correct. Artifact repositories provide durable storage for files passed between workflow tasks.

  2. B To hold Argo CD user accounts and RBAC policies.

    Incorrect. Argo CD account and RBAC configuration is not stored in the workflow artifact repository.

  3. C To replace every Kubernetes `PersistentVolumeClaim` in the cluster.

    Incorrect. Artifact repositories do not replace all persistent volumes in a cluster.

  4. D To provide traffic routing for blue-green deployments.

    Incorrect. Blue-green traffic routing is a Rollouts concern.

  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. A template references an image by tag `latest`, and reruns unexpectedly use different code. Which workflow-design improvement is most appropriate?

Reveal answer and explanations
  1. A Set `selfHeal: true` in the workflow spec.

    Incorrect. `selfHeal` is an Argo CD automated sync option, not a workflow image-pinning feature.

  2. B Replace every template with a Sensor trigger.

    Incorrect. Sensor triggers do not solve mutable image tag reproducibility.

  3. C Use immutable image references or pass explicit version parameters.

    Correct. Explicit immutable versions make workflow reruns more reproducible.

  4. D Disable the workflow controller's pod watch.

    Incorrect. Disabling pod watching would break workflow reconciliation rather than fix image drift.

  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 does a script template's `outputs.result` commonly contain?

Reveal answer and explanations
  1. A The full Kubernetes audit log for the workflow namespace.

    Incorrect. Workflow scripts do not capture namespace audit logs into `outputs.result`.

  2. B The generated Argo CD `Application` resource for the script.

    Incorrect. Script templates do not automatically generate Argo CD Applications.

  3. C The current canary traffic weight for a Rollout.

    Incorrect. Canary weights are not stored as script template results.

  4. D The script's standard output captured as a small output parameter.

    Correct. Argo can capture script standard output into `outputs.result` for later template references.

  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 workflow-level `parallelism` value is set lower than the number of ready DAG tasks. What happens?

Reveal answer and explanations
  1. A The workflow is invalid because DAGs cannot limit parallelism.

    Incorrect. DAG workflows can still use parallelism limits.

  2. B Argo limits how many pods/nodes from the workflow run concurrently even if more tasks are ready.

    Correct. Workflow parallelism throttles concurrent execution even when the dependency graph has more runnable nodes.

  3. C Argo CD disables automated sync for the namespace.

    Incorrect. Argo CD sync settings are unrelated to workflow parallelism.

  4. D The Rollouts controller takes over task scheduling.

    Incorrect. Rollouts does not schedule Workflow DAG tasks.

  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. What is a common reason to use Argo Workflows in a CI/CD pipeline?

Reveal answer and explanations
  1. A To make Kubernetes accept imperative `kubectl edit` operations as GitOps changes.

    Incorrect. Argo Workflows does not turn imperative cluster edits into GitOps state.

  2. B To orchestrate multi-step build, test, scan, and release jobs as Kubernetes-native tasks.

    Correct. Workflows can model CI/CD jobs as repeatable task graphs running in Kubernetes.

  3. C To automatically replace all application manifests with Helm charts.

    Incorrect. Workflows can run Helm-related tasks but do not automatically replace manifest formats.

  4. D To disable workflow pod logs after each task completes.

    Incorrect. Workflow observability usually benefits from retaining or archiving relevant logs.

  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.

Drill Argo Workflows with the full bankDomain Drill mode targets your weak areas — paid feature

How this domain is tested

Argo Workflows accounts for 36% of the CAPA exam. Expect questions that test recall of terminology and the ability to read short scenarios — not deep configuration. Use the sample questions above as difficulty calibration; if any feel hard, the rest of our 44-question domain bank will close those gaps.