Certified Argo Project Associate (CAPA) free question 5 / 10 · Domain 2: Argo CD
A team added a smoke test that must run after each deployment as a lifecycle event of the sync. Which Argo CD component is responsible for invoking that user-defined hook?
- The API server, which authenticates users and forwards Git webhook events
- The application controller, which also watches running applications for OutOfSync state
- The repository server, which generates the manifests and keeps the local Git cache
- The Git provider, which fires the hook when the commit reaches the tracked branch
Show the answer and explanation
Answer: B
Why this is correct
The Architectural Overview describes the application controller as a Kubernetes controller that continuously monitors running applications and compares the current, live state against the desired target state specified in the repository. It detects an OutOfSync state and optionally takes corrective action. The same paragraph says it is responsible for invoking any user-defined hooks for lifecycle events, namely PreSync, Sync and PostSync.
Why the other options are wrong
"The repository server, which generates the manifests and keeps the local Git cache" … The repository server returns manifests for the inputs it receives. The page does not make it responsible for lifecycle hooks.
"The API server, which authenticates users and forwards Git webhook events" … The API server can invoke operations such as sync, but running the PreSync, Sync and PostSync hooks is listed under the application controller.
"The Git provider, which fires the hook when the commit reaches the tracked branch" … A Git webhook only tells Argo CD that something changed. The overview names the application controller as the invoker of lifecycle hooks.
Key points
The component that compares states is also the one that runs lifecycle hooks. Hooks are not part of manifest generation.