Exactprep CGOA Questions

In GitOps, Continuous Deployment (CD) follows after Continuous Integration (CI). CI is responsible for building and testing application code, while CD automates the delivery and deployment of these changes into runtime environments. The Git repository serves as the single source of truth, and when CI merges new changes into the main branch, CD reconciles the state of the environment to match what is declared in Git.

“GitOps builds on the principles of DevOps by using Git as the source of truth for declarative infrastructure and applications. CI pipelines handle the integration and testing of code, and CD pipelines or agents automatically reconcile the desired state in Git with the actual state in the cluster.”

This shows that CD is triggered after CI to handle deployment automation, ensuring systems remain in sync with what is declared in version control.

GitOps enhancesDevSecOpsby ensuring security-related configurations and changes are stored in version control, where acomplete audit historyis available. This provides traceability, accountability, and compliance enforcement.

“With GitOps, the entire version history of desired state changes is stored immutably in Git. This audit trail supports security and compliance goals in DevSecOps practices.”

Thus, the correct answer isB.

TheDesired Statein GitOps is the declarative specification of how the system should behave. It is stored in Git and serves as the reference point for reconciliation against the actual state.

“The desired state is a complete specification of the system stored in Git. It acts as the blueprint from which the actual state is continuously reconciled, ensuring the system remains consistent and reproducible.”

Thus, theprimary purpose of Desired Stateis to act as ablueprintto recreate and ensure consistency of the system.

The core foundation of GitOps is that Git serves as the single source of truth for the desired state of both applications and infrastructure. This means all configuration is declared in Git in a version-controlled, auditable, and verifiable manner. Operators and reconciliation agents continuously pull these definitions to ensure the live system matches what Git declares.

“Declarative descriptions of the desired state of the system must be versioned in Git, making Git the single source of truth. This provides auditability, reliability, and enables rollbacks by reverting changes in Git.”

This principle ensures that any change in system state is traceable through Git commits, making environments predictable, reproducible, and transparent.