Free Practice Questions for Linux Foundation CGOA Exam

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.

Kustomizeis a Kubernetes-native configuration management tool that allows manifest customization without modifying the original YAML files. It uses overlays and patches to adapt configurations for different environments.

“Kustomize provides a declarative way to customize Kubernetes manifests by applying patches and overlays. This allows managing multiple environments without duplicating manifest files.”

Thus, the correct answer isD.

GitOps emphasizes immutability and auditability. If an error occurs in the configuration stored in Git, the system should be rolled back to the last known good state while the error is fixed. This preserves system reliability and aligns with the GitOps principle of rollback through version control.

“With Git as the source of truth, if an error is introduced, the system can be rolled back by reverting to a previous commit. This ensures stability while the faulty configuration is corrected.”

Thus, the recommended action isC: Roll back to the previous working version.

In GitOps, deployments are driven bycommitting declarative configurationinto 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 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, 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.

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.

Progressive deliveryis a GitOps pattern that incrementally rolls out application updates, using methods like canary releases, feature flags, and blue-green deployments. GitOps enhances this by ensuring the rollout isautomated and declaratively managed through Git, removing the need for manual traffic switching.

“GitOps enables progressive delivery by declaratively managing rollout strategies such as canary or blue-green deployments. These strategies are applied automatically by controllers, without requiring manual traffic switching.”

Thus, the correct answer isB.

Configuration as Code (CaC)in GitOps ensures that infrastructure and application definitions are stored in Git, version-controlled, and immutable. Unlike traditional approaches (manual changes, scripts, mutable infrastructure), GitOps uses CaC forimmutable infrastructure deployments, guaranteeing reproducibility and environment consistency.

“Configuration as Code ensures that system configuration is stored declaratively in version control. This allows immutable deployments, reproducibility, consistency across environments, and prevents ad-hoc manual changes.”

Thus, the distinct advantage isimmutable deployments and consistent environments, makingBcorrect.