← CAPA hub

CAPA — ARGO CD

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

Sample questions on ARGO CD

ARGO CD

Q1. What does the `prune` option do when enabled for Argo CD sync?

Reveal answer and explanations
  1. A It pauses a canary Rollout after a traffic weight step.

    Incorrect. Pausing canaries is a Rollouts behavior.

  2. B It removes old Workflow pods from the workflow archive.

    Incorrect. Workflow pod retention is not controlled by Argo CD prune.

  3. C It deletes live resources that were previously managed but no longer exist in the desired state.

    Correct. Pruning removes managed resources that disappeared from the desired manifests.

  4. D It removes all Git history from the configured repository.

    Incorrect. Argo CD does not rewrite or remove Git repository history.

  5. E Run the workload through Argo Workflows first and let completed pods become the source of truth that Argo CD reconciles into the cluster.

    Incorrect. Argo CD reconciles desired state from configured sources such as Git, not from completed workflow pods.

ARGO CD

Q2. A team wants Argo CD to create the destination namespace if it does not exist. Which sync option is commonly used?

Reveal answer and explanations
  1. A `CreateNamespace=true`

    Correct. The `CreateNamespace=true` sync option asks Argo CD to create the destination namespace during sync.

  2. B `autoPromotionEnabled=false`

    Incorrect. `autoPromotionEnabled` is an Argo Rollouts blue-green option.

  3. C `withParam`

    Incorrect. `withParam` is an Argo Workflows loop construct.

  4. D `eventBusName=default`

    Incorrect. `eventBusName` selects an Argo Events bus and does not create namespaces for Argo CD.

ARGO CD

Q3. Which command is commonly used to manually synchronize an Argo CD Application from the CLI?

Reveal answer and explanations
  1. A `argocd app sync`

    Correct. `argocd app sync` starts synchronization for an Argo CD Application.

  2. B `argo submit`

    Incorrect. `argo submit` submits an Argo Workflow.

  3. C `kubectl argo rollouts set image`

    Incorrect. Rollouts plugin commands operate on Rollout resources, not Argo CD Application sync.

  4. D `argo sensor sync`

    Incorrect. `argo sensor sync` is not the normal Argo CD sync command.

ARGO CD

Q4. An Application has a Helm chart source and a `values.yaml` override. Where should Argo CD render the final manifests before sync?

Reveal answer and explanations
  1. A In the repo-server, using the configured source and Helm settings.

    Correct. Repo-server renders Helm, Kustomize, and other supported sources into Kubernetes manifests for Argo CD.

  2. B Inside every target application pod at startup.

    Incorrect. Application pods should receive already-applied Kubernetes manifests, not render Helm at startup.

  3. C Inside the EventBus before Sensors evaluate dependencies.

    Incorrect. EventBus is unrelated to Argo CD manifest rendering.

  4. D Inside the Rollouts controller during traffic shifting.

    Incorrect. Rollouts controller manages progressive delivery and does not render Helm charts for Argo CD.

  5. E Run the workload through Argo Workflows first and let completed pods become the source of truth that Argo CD reconciles into the cluster.

    Incorrect. Argo CD reconciles desired state from configured sources such as Git, not from completed workflow pods.

ARGO CD

Q5. What does `targetRevision` specify in an Argo CD Application source?

Reveal answer and explanations
  1. A The Kubernetes API version used by the Application CRD.

    Incorrect. CRD API version is declared in `apiVersion`, not `targetRevision`.

  2. B The desired replica count for all Deployments in the Application.

    Incorrect. Replica counts are part of workload manifests, not `targetRevision`.

  3. C The Rollout revision that should receive stable traffic.

    Incorrect. Rollout traffic revisions are not selected by Argo CD `targetRevision`.

  4. D The branch, tag, commit, chart version, or similar source revision to render.

    Correct. `targetRevision` tells Argo CD which source revision to use when rendering desired state.

  5. E Run the workload through Argo Workflows first and let completed pods become the source of truth that Argo CD reconciles into the cluster.

    Incorrect. Argo CD reconciles desired state from configured sources such as Git, not from completed workflow pods.

Drill ARGO CD with the full bankDomain Drill mode targets your weak areas — paid feature

How this domain is tested

ARGO CD accounts for 34% 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 40-question domain bank will close those gaps.