Certified Argo Project Associate (CAPA) free question 7 / 10 · Domain 2: Argo CD
An operator wants to know how Argo CD calculates the diff between the desired and the live state by default, before any Server-Side Apply option is enabled. Which strategy applies?
- The Legacy strategy, a 3-way diff of the live state, the desired state and the last-applied-configuration annotation
- The Server-Side Diff strategy, which runs a dry-run Server-Side Apply for the resources of the application
- A 2-way diff that compares the desired state with the live state and does not read an annotation of the resource
- The Structured-Merge Diff strategy, which compares the fields owned by a manager of the live resource
Show the answer and explanation
Answer: A
Why this is correct
The Diff Strategies page says Argo CD calculates the diff between the desired state and the live state to define whether an Application is out of sync, and the same logic is used in the UI to show the differences. It lists three strategies. Legacy is the main strategy used by default and applies a 3-way diff based on the live state, the desired state and the last-applied-configuration annotation. Structured-Merge Diff is discontinued. Server-Side Diff invokes a Server-Side Apply in dry-run mode to generate the predicted live state.
Why the other options are wrong
"The Server-Side Diff strategy, which runs a dry-run Server-Side Apply for the resources of the application" … Server-Side Diff is used automatically when the Server-Side Apply sync option is enabled. The default is Legacy.
"The Structured-Merge Diff strategy, which compares the fields owned by a manager of the live resource" … That strategy is discontinued and was superseded by Server-Side Diff. It is not the default.
"A 2-way diff that compares the desired state with the live state and does not read an annotation of the resource" … The default strategy is a 3-way diff that also uses the last-applied-configuration annotation.
Key points
Default is Legacy with a 3-way diff. Server-Side Diff arrives with the Server-Side Apply sync option.