A version controlled Git repository containing the declarative manifests and configuration is the authoritative record of application code configuration and the desired cluster state in a GitOps process.

The Git repository acts as the single source of truth and it provides history, auditability, and a clear change approval flow through commits and pull requests. Storing declarative manifests and configuration in version control enables reproducible environments, easy rollbacks, and automated reconciliation by GitOps operators.

In a GitOps workflow the repository holds the desired state and continuous delivery agents reconcile the cluster to match that state. The repository also integrates with CI pipelines so that built artifacts and configuration changes are coordinated and traceable back to specific commits.

Kubernetes manifests applied to the cluster without being stored in version control is incorrect because applying manifests only to the cluster does not provide a versioned, auditable source of truth. Without the repository you lose repeatability and a clear history of changes.

Cloud Build trigger configuration is incorrect because build triggers are part of the CI execution and they do not represent the declarative desired state of the cluster. They may start pipelines but they are not the authoritative record of manifests and configuration.

Argo CD application configuration is incorrect as the authoritative record because Argo CD is a synchronization tool that uses a source repository as the truth. Argo CD application objects can describe how to sync from Git, but the recommended GitOps pattern keeps the declarative manifests in the version controlled repository as the source of truth.

Full AWS Practitioner Certification Question