Cheat sheet & self-check

Pick an answer to see if you got it, and why.

1. Q1. In the lab, where does Argo CD run and where do the apps run?

   1. ABoth on one cluster
   2. BArgo CD on a tools cluster; apps on a separate target cluster it registered with argocd cluster add
   3. COn the Git server
   4. DOn the developer laptop
   Show answer

   B. Hub and spoke: one Argo CD manages other clusters through credentials stored when the cluster is registered.

   From lesson 09 · Hands-on lab: Argo CD deploying to a second cluster

2. Q2. Why does the lab use two repositories: an app repo and a deploy repo?

   1. AGit requires it
   2. BThe app repo holds code and CI builds the image; the deploy repo holds only desired state that Argo CD applies, and needs no pipeline
   3. CArgo CD can only read one file per repo
   4. DTo save disk space
   Show answer

   B. Separating code from desired state keeps CI and CD independent, as the GitOps track explains.

   From lesson 09 · Hands-on lab: Argo CD deploying to a second cluster

3. Q3. What is the recommended way to roll back in the lab, and why?

   1. Aargocd app rollback, because it's faster
   2. Bgit revert, so Git and the cluster stay equal; a UI rollback needs auto-sync off and is undone by the next sync
   3. CDelete the app
   4. Dkubectl rollout undo
   Show answer

   B. In GitOps the rollback is a Git change. UI rollback is for emergencies only.

   From lesson 09 · Hands-on lab: Argo CD deploying to a second cluster