Free Practice Questions for Linux Foundation CGOA Exam

The two most widely adopted GitOps controllers in the CNCF ecosystem areArgoCDandFlux. Both implement the GitOps principles of continuous reconciliation from Git as the source of truth.

“ArgoCD and Flux are the two primary CNCF GitOps controllers. They implement reconciliation loops to ensure the desired state in Git matches the cluster’s actual state.”

Thus, the correct answer isC.

In GitOps,Git is the single source of truth. If changes are made manually in the cluster (viakubectl), those changes will drift from the desired state in Git. To ensure consistency, the correct approach is toupdate the Git repository (Desired State store)so that the reconciler can continuously apply and maintain those changes.

“The desired state must always be declared in Git. Manual changes in the cluster will be overwritten by reconciliation unless they are committed to the Git repository.”

Thus, the correct answer isB.

Areconcilerensures that the actual system matches the desired state declared in Git. External reconcilers run outside the core cluster orchestration process.Fluxis a widely used GitOps external reconciler that continuously syncs cluster state with the repository.

“Flux is an example of a GitOps reconciler that continuously monitors Git repositories and applies changes to the cluster. As an external reconciler, it handles synchronization and reconciliation loops outside the direct application code.”

Thus,A: Fluxis correct.

Linting tools are essential in GitOps practices for maintaining consistency, standardization, and quality in configuration files. Automated linters can validate YAML manifests, Helm charts, or Kustomize overlays for formatting and best practices.

“Linters automate the enforcement of formatting and quality rules in declarative configuration files. They ensure standardized structure and reduce errors in GitOps workflows.”

Thus, the correct answer isC.

In GitOps, rollback is performed by reverting the system’sDesired Statestored in Git. This is done with thegit revertcommand, which creates a new commit that undoes the changes introduced by a previous commit.

“Because Git provides an immutable history of changes, rollbacks are straightforward. Reverting to a previous configuration is accomplished by reverting the commit in Git, which then allows the reconciler to apply the earlier desired state.”

Thus, the correct answer isB: git revert.

In GitOps,everything that defines the system, including dashboards, must be stored declaratively in Git(the Desired State store). This ensures dashboards are versioned, reproducible, and consistent across environments.

“GitOps requires that all system components, including monitoring and observability configurations such as dashboards, are declared in Git. This ensures they are versioned, immutable, and reproducible.”

Thus,Dis correct.

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.

Prometheus is commonly used in GitOps for monitoring.Alertmanageris the tool integrated with Prometheus to handle alert routing. It supports sending alerts to external systems such as Slack, PagerDuty, or email.

“Prometheus generates alerts, which are routed and managed by Alertmanager. Alertmanager can integrate with messaging tools like Slack to deliver alerts in real time.”

Thus, the correct answer isA: Alertmanager.