GitOps interview questions
4 questions interviewers actually ask, each with a model answer you can study and an AI drill that grades how you would say it out loud.
0/4
Mastered
Questions and answers
Model answer
The desired state is declarative, versioned and immutable in git, pulled automatically by agents, and continuously reconciled so the running system matches git. Git becomes the single source of truth and a full audit log, and changes happen through pull requests rather than manual cluster edits.
Model answer
It removes manual, drift-prone cluster changes by making git the source of truth, so deployments are reviewable, auditable, and easy to roll back by reverting a commit. Reconciliation also auto-heals drift, and recovery becomes pointing a fresh cluster at the repo. It brings software engineering discipline to operations.
Model answer
Argo CD runs in the cluster and watches a git repo of manifests. It continuously compares the desired state in git with the live cluster state, reports sync and health status, and can automatically apply changes and self-heal drift. Operators push changes to git via pull request and Argo reconciles the cluster.
Model answer
Never store plaintext secrets in git. Encrypt them so only the cluster can decrypt, using tools like Sealed Secrets, or keep secret material in an external store and reference it with the External Secrets Operator, which injects real values at runtime. The encrypted reference lives in git; the secret never does.