Free Linux Foundation CGOA Practice Exam with Questions & Answers | Set: 2

The GitOps principle ofVersioned and Immutablerequires Desired State to be stored in a way that enforcesimmutability and versioning. This ensures every change is recorded, auditable, and reversible.

“Desired state must be kept in an immutable, version-controlled system. This guarantees a full history of changes and enables safe rollbacks.”

Thus, the correct answer isD.

In GitOps, systems are defined declaratively. This means that thedesired stateis described in Git, while the steps to achieve it are not explicitly defined. Instead, reconciliation agents interpret the declarative definition and automatically apply changes as needed.

“A declaratively defined system specifies only the desired state. It does not describe the sequence of steps required to reach that state. The reconciliation process ensures the system converges to the declared state automatically.”

Therefore, the correct answer isC: Only the Desired State.

Progressive deliveryis a GitOps pattern used to release software gradually, reducing risks associated with deploying new versions. Techniques such as canary releases, feature flags, and blue-green deployments allow teams to incrementally roll out changes, validate functionality with subsets of users, and minimize potential disruptions.

“Progressive delivery builds on continuous delivery by enabling safer, incremental rollouts. This pattern reduces risk, improves reliability, enhances user experience, and allows for validation of features with a portion of users before wider release.”

Therefore, progressive delivery is useful inmultiple scenarios(not just one-time deployments or small teams), making optionCcorrect.

Continuous reconciliationis another core GitOps principle. It means that software agents (operators or controllers) run loops that continuously observe the live system and compare it against the desired state declared in Git. If any divergence (drift) is found, the agentautomatically reconcilesthe system to match the declared configuration.

“Software agents continuously observe the actual system state and compare it with the desired state declared in Git. If a divergence is detected, the agents automatically reconcile the difference to bring the system back into alignment.”

This providesautomation, consistency, and self-healing, which are hallmarks of GitOps.

A fundamental GitOps principle is that reconciliation isautomated and continuous. Software agents (e.g., controllers like ArgoCD or Flux) continuously pull desired state declarations from Git repositories and reconcile them with the actual state.

“Software agents automatically pull the desired state declarations from the source of truth and continuously reconcile the actual state to match.”

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.

Declarative configuration describeswhatthe system should look like, nothowto achieve it. This enables the use ofstandard 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 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.