Which statement defines GitOps in deployment workflows?

Which statement defines GitOps in deployment workflows?

• A. Manual synchronization to environments.
• B. Storing code in a version control system but not using automation.
• C. Desired state stored in Git with automated synchronization to environments.
• D. A runtime policy for container images.

Answer: (C)

GitOps hinges on declaring the desired state of your systems in Git and letting automation reconcile that state in your environments. In this approach, every change is a Git commit or pull request, which provides a single, versioned source of truth and an auditable history. An automated agent continuously monitors the repository and the target environment, and when the desired state changes, it applies updates to bring the live system into alignment with what Git specifies. This pull-based, automated reconciliation enables reproducible deployments, easier rollbacks by reverting commits, and consistent behavior across environments. The other statements don’t fit because manual synchronization relies on human steps and lacks automation, storing code without automation misses the reconciliation loop, and a runtime policy for container images describes runtime governance rather than the declarative, automated deployment model GitOps uses.

GitOps hinges on declaring the desired state of your systems in Git and letting automation reconcile that state in your environments. In this approach, every change is a Git commit or pull request, which provides a single, versioned source of truth and an auditable history. An automated agent continuously monitors the repository and the target environment, and when the desired state changes, it applies updates to bring the live system into alignment with what Git specifies. This pull-based, automated reconciliation enables reproducible deployments, easier rollbacks by reverting commits, and consistent behavior across environments. The other statements don’t fit because manual synchronization relies on human steps and lacks automation, storing code without automation misses the reconciliation loop, and a runtime policy for container images describes runtime governance rather than the declarative, automated deployment model GitOps uses.