Explain GitOps and how an agent knows when to apply changes

Tests whether you understand declarative infrastructure and the pull-based reconciliation loop that separates GitOps from CI/CD. A strong answer covers four things in order: first, Git is the single source of truth; second, the agent polls the repo or uses webhooks to detect commits; third, it compares desired state in Git against actual cluster state; fourth, it applies changes when drift is detected. Red flag: describing a push-based CI pipeline where Jenkins runs kubectl apply as GitOps, which misses reconciliation and self-healing.