CGOA Sample Questions Answers

TheState Storeis typically implemented using aversion control system (VCS)such as Git. This ensures that the system’s state is auditable, versioned, and immutable. Other systems like databases or distributed file systems do not meet the immutability and versioning requirements of GitOps.

“In GitOps, the desired state must be stored in a version control system. This serves as the State Store, providing a complete, immutable, and auditable history of changes.”

Thus, the correct answer isD: version control system.

GitOps requires apull-based approachas the default model, where agents in the cluster automatically pull desired state from Git. However,push-based triggers(e.g., webhooks) can optionally be used to complement pull-based reconciliation.

“Pull-based reconciliation is required in GitOps to ensure automation and security. Push-based triggers may optionally complement this, but the pull model is fundamental.”

Thus, the correct answer isD.

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.

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.

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.

Whendriftoccurs (actual state diverges from desired state), GitOps controllers attempt to reapply theDesired Statestored in Git. The system is always converged toward what Git declares, never the other way around.

“In case of drift, the reconciler re-applies the desired state from Git to the runtime environment, ensuring the actual system matches the declared configuration.”

Thus, the correct answer isB.

Kustomize is a GitOps tool for managing Kubernetes configurations declaratively. It uses afolder structure with configuration filesand akustomization.yamlfile 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 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.

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, thepull-based modelcontinuously reconciles the actual state with the desired state. This makes it resilient to drift, since reconciliation runs regularly. In contrast,event-driven systemsonly reconcile when an event occurs (e.g., a webhook), which makes them more prone to drift if changes happen outside those events.

“A pull-based reconciliation loop ensures continuous alignment with the desired state. Event-driven reconciliation, triggered only on events, risks system drift if changes occur outside those triggers.”

Thus, the correct answer isD.

One of the GitOps principles isVersioned and Immutable, which requires that the Desired State is stored in a system that maintains acomplete 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 isB.

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.

One of the four core GitOps principles is that the system must beContinuously Reconciled. This means reconciliation is not a one-time or on-demand process but happensconstantlyin the background, ensuring the actual system state remains aligned with the declared desired state.

“GitOps requires that reconciliation is continuous. Software agents continuously compare actual state against desired state and automatically reconcile differences.”

Thus, the correct answer isC.

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.

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.