Free Practice Questions for the Linux Foundation DevOps and Site Reliability CGOA Exam (2026 Updated)

The Pulled Automatically GitOps principle refers to the way software agents continuously access the Desired State stored in the State Store (e.g., Git). Agents automatically pull the state from the repository and reconcile the system accordingly.

“Software agents automatically pull the desired state declarations from the source of truth (State Store) and continuously reconcile the system to match.”

Thus, the correct answer is D .

A reconciler ensures that the actual system matches the desired state declared in Git. External reconcilers run outside the core cluster orchestration process. Flux is 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: Flux is correct.

In GitOps, deployments are driven by committing declarative configuration into a Git repository (the State Store). From there, agents reconcile the actual environment to match the desired state, making deployments reproducible and auditable.

“To deploy in GitOps, commit the declarative configuration into version control. The reconciler ensures the runtime environment converges to the declared state.”

Thus, the correct answer is D .

In GitOps, pull-based deployment is fundamental. Instead of pushing changes into a cluster, GitOps agents running inside the cluster continuously pull from Git to reconcile desired state.

“GitOps uses a pull-based model: agents inside the cluster continuously poll the Git repository for desired state changes. If changes are found, they reconcile the live system automatically to match the declared state.”

This ensures secure, automated, and consistent deployments.

Thus, D is correct.

Declarative configuration describes what the system should look like, not how to achieve it. This enables the use of standard reconciliation tools (like ArgoCD or Flux) to manage the system automatically, removing the burden of writing and maintaining imperative scripts.

“Declarative configuration enables systems to be managed by generic reconciliation tools rather than bespoke scripts, reducing operational overhead and increasing reliability.”

Thus, the correct answer is B .

Although reconciliation is continuous in GitOps, tools often allow reconciliation to be triggered earlier than the normal polling interval. The recommended approach is to use webhooks from the Git repository , which notify the GitOps controller of changes and trigger an immediate reconcile.

“While reconciliation loops continuously compare desired and actual state, reconciliation can be triggered sooner by webhooks from version control events, ensuring timely application of changes.”

Thus, the correct answer is A .

Kustomize is a GitOps tool for managing Kubernetes configurations declaratively. It uses a folder structure with configuration files and a kustomization.yaml file that references resources and overlays. This enables customization without modifying the base manifests.

“Kustomize allows customization of Kubernetes manifests by organizing resources in directories and referencing them through file paths in a kustomization file. This directory-based approach supports overlays, reusability, and modular configuration.”

Thus, the correct answer is D .

The feedback loop is critical in GitOps reconciliation. It continuously monitors the system’s actual state and compares it to the desired state. This loop determines when reconciliation is required and whether a full or partial synchronization is necessary.

“The feedback loop in reconciliation continuously observes the actual state. It determines if reconciliation is required, and informs whether to perform a partial or full sync to align with the declared desired state.”

Thus, the correct answer is A .

In a Blue-Green deployment , two environments (Blue and Green) exist at the same time. The current version runs in one environment (Blue), and the new version is deployed to the other environment (Green). Traffic is switched to Green once the new version is validated.

“Blue-Green deployments maintain two production environments. The new version is deployed alongside the old version, and once validated, traffic is switched from Blue to Green.”

Thus, the correct answer is C .

Helm is a Kubernetes package manager widely used in GitOps for packaging, configuring, and deploying complex applications. Helm charts bundle configuration, dependencies, and Kubernetes manifests into reusable, declarative packages that can be applied across multiple clusters.

“Helm charts provide a way to package Kubernetes applications, defining configuration and dependencies declaratively. This allows consistent deployment across clusters in GitOps workflows.”

Thus, the correct answer is A .

GitOps enhances DevSecOps by ensuring security-related configurations and changes are stored in version control, where a complete audit history is 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 is B .

The Desired State is the declarative specification stored in Git that defines how the system should look and behave. It is the reference point against which the actual state is continuously reconciled.

“Desired state is the complete declarative specification of a system stored in Git. It defines how the system should be configured and serves as the source of truth for reconciliation.”

Thus, the correct answer is A .

One of the GitOps principles is Versioned and Immutable , which requires that the Desired State is stored in a system that maintains a complete version history . This allows for auditing, traceability, and rollback.

“The Desired State must be stored in a versioned, immutable system. The State Store must retain a complete version history so changes can be audited and previous states can be restored.”

Thus, the correct answer is B .

DevSecOps integrates security into the DevOps culture and CI/CD pipelines. Instead of treating security as an afterthought, DevSecOps ensures security checks, policies, and automated validations are embedded throughout the CI/CD process.

“DevSecOps emphasizes shifting security left, integrating security testing, validation, and compliance into every stage of the CI/CD pipeline. This ensures vulnerabilities are detected early and software is delivered securely.”

Thus, D is correct: DevSecOps culture is essential for CI/CD pipelines to ensure security is baked into software delivery.

ArgoCD and Flux are the two primary CNCF GitOps tools. While both are reconciliation engines, they can be used together carefully if configured properly to avoid conflicts. For example, Flux can be used to manage configuration sources, while ArgoCD handles application-level delivery. Extensions and integration points allow them to complement each other.

“ArgoCD and Flux implement the GitOps reconciliation principle. Though they provide overlapping functionality, they can be integrated by carefully managing their scope. For instance, Flux can manage sources and Helm charts, while ArgoCD handles higher-level deployments. Extensions exist to allow cooperation without conflict.”

Thus, the correct answer is C .