Certified Argo Project Associate (CAPA) free question 9 / 10 · Domain 3: Argo Rollouts
An AnalysisRun completes during a canary update. How does the final phase of the run affect the Rollout's update?
- Successful and Inconclusive let the update continue, and Failed pauses it for a manual decision
- Successful ends the update at the first measurement, Failed pauses it, and Inconclusive aborts it
- Failed and Inconclusive abort the update, and Successful continues it
- Successful lets the update continue, Failed aborts it, and Inconclusive pauses it
Show the answer and explanation
Answer: D
Why this is correct
The Analysis page describes an AnalysisRun as an instantiation of an AnalysisTemplate that, like a Job, eventually completes. A completed run is Successful, Failed or Inconclusive, and these results map to continue, abort and pause respectively. The Inconclusive case lets automation collect measurements while a human still decides whether the value is acceptable.
Why the other options are wrong
"Successful ends the update at the first measurement, Failed pauses it, and Inconclusive aborts it" … Failed and Inconclusive are mixed up here. A failed run aborts the update, and an inconclusive run pauses it so that a person can decide.
"Successful and Inconclusive let the update continue, and Failed pauses it for a manual decision" … An inconclusive run is neither a success nor a failure, so the rollout stops at its current step. A failed run aborts the rollout.
"Failed and Inconclusive abort the update, and Successful continues it" … Only a failed run aborts. An inconclusive run pauses the rollout at the current step, and manual intervention resumes it or aborts it.
Key points
Successful = continue, Failed = abort, Inconclusive = pause for a human decision.