← CAPA hub

CAPA — Argo Rollouts

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

Sample questions on Argo Rollouts

Argo Rollouts

Q1. Which command is commonly used to watch rollout progress with the kubectl plugin?

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

    Incorrect. `argocd app diff` compares desired and live Argo CD state.

  2. B `argo submit --watch`

    Incorrect. `argo submit --watch` follows a workflow, not a Rollout.

  3. C `kubectl get sensor --watch`

    Incorrect. Watching Sensors does not show Rollout progression.

  4. D `kubectl argo rollouts get rollout --watch`

    Correct. The Rollouts kubectl plugin can display rollout status and watch its progression.

Argo Rollouts

Q2. Why should analysis success conditions be specific rather than merely checking that a metric query returned data?

Reveal answer and explanations
  1. A Returned data is always a Kubernetes object, not a metric.

    Incorrect. Metric query results are not necessarily Kubernetes objects.

  2. B Sensors cannot trigger Workflows when metrics have labels.

    Incorrect. Sensor triggering is not limited this way by metric labels.

  3. C Argo CD refuses to sync Applications with analysis conditions.

    Incorrect. Argo CD sync does not reject Applications because a Rollout has analysis conditions.

  4. D A non-empty result may still represent an unhealthy error rate or latency value.

    Correct. Analysis needs explicit success and failure logic so bad metric values do not pass merely because data exists.

Argo Rollouts

Q3. Why might a Rollout integrate with an ingress controller or service mesh?

Reveal answer and explanations
  1. A To perform fine-grained traffic splitting between stable and canary versions.

    Correct. Traffic integrations allow Rollouts to shift request traffic precisely during progressive delivery.

  2. B To store workflow artifacts in an object bucket.

    Incorrect. Artifact storage is an Argo Workflows concern.

  3. C To create Argo CD Applications from a Git generator.

    Incorrect. Application generation belongs to Argo CD ApplicationSet.

  4. D To receive CloudEvents from external systems.

    Incorrect. CloudEvent reception is handled by Argo Events.

Argo Rollouts

Q4. A Deployment is changed into a Rollout but the old Deployment object remains managing the same selector. What is the risk?

Reveal answer and explanations
  1. A Two controllers may fight over matching ReplicaSets or pods, causing unstable rollout behavior.

    Correct. Controllers with overlapping selectors can conflict, so migrations must avoid dual ownership.

  2. B The EventBus will duplicate every webhook message.

    Incorrect. EventBus message duplication is unrelated to Deployment-to-Rollout migration.

  3. C The Workflow controller will delete both resources immediately.

    Incorrect. The Workflow controller does not delete Deployment or Rollout resources.

  4. D Argo CD will stop rendering all Helm charts in the repo.

    Incorrect. Helm rendering is not affected by overlapping workload selectors.

Argo Rollouts

Q5. What does a `setWeight` step usually express in a canary rollout?

Reveal answer and explanations
  1. A The number of workflow artifacts to keep in object storage.

    Incorrect. Artifact retention is not configured with `setWeight`.

  2. B The percentage of traffic or replica weighting assigned to the canary at that step.

    Correct. `setWeight` moves the canary to a specified percentage during rollout progression.

  3. C The priority of an Argo Events Sensor dependency.

    Incorrect. Sensor dependencies do not use Rollout `setWeight`.

  4. D The sync wave number for an Argo CD resource.

    Incorrect. Sync waves are Argo CD annotations, not canary weight steps.

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

How this domain is tested

Argo Rollouts accounts for 18% 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 22-question domain bank will close those gaps.