Linux Foundation CGOA Exam Practice Test Instant Access

Question 1

Which GitOps tool has the option for a push-based reconciliation model?

AArgoCD

BFlagger

CFlux

DArgo Workflows

Answer : A

Most GitOps tools (e.g., Flux) are pull-based only. However, ArgoCD supports both pull-based reconciliation (via continuous monitoring) and an optional push-based model, where changes can be triggered via webhooks or CI pipelines.

''ArgoCD supports both pull-based reconciliation, where the controller watches the repository, and an optional push-based reconciliation mode triggered by webhooks.''

Thus, the correct answer is A: ArgoCD.

Question 2

Which deployment and release pattern involves gradually shifting traffic from an old version of an application to a new one?

ARed/Black Deployment

BCanary Deployment

CBlue-Green Deployment

DA/B Deployment

Answer : B

A Canary Deployment gradually introduces a new application version to a small subset of users before expanding to the full user base. This pattern allows testing and validation in production while reducing risk.

''Canary deployments progressively roll out changes to a small group of users, monitoring for issues before routing all traffic to the new version. This gradual shift minimizes risk and ensures safer releases.''

Thus, the correct answer is B.

===========

Question 3

You are working on a GitOps project and need to understand the similarities and differences between pull-based messaging systems and event-driven systems. What is a key difference between these two types of systems?

APull-based systems require a constant network connection to receive updates.

BEvent-driven systems are less flexible and scalable compared to pull-based systems.

CPull-based systems are more efficient in handling real-time events.

DWhen only events trigger reconciliation, the system is more vulnerable to drift caused by other things.

Answer : D

In GitOps, the pull-based model continuously reconciles the actual state with the desired state. This makes it resilient to drift, since reconciliation runs regularly. In contrast, event-driven systems only 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 is D.

===========

Question 4

In the context of GitOps, which of the following is the primary purpose of Desired State?

ATo serve as a blueprint to recreate a system for behavioral consistency.

BTo store all persistent application data, such as database content.

CFor monitoring real-time application performance.

DTo track code changes that developers have made.

Answer : A

The Desired State in GitOps is the declarative specification of how the system should behave. It is stored in Git and serves as the reference point for reconciliation against the actual state.

''The desired state is a complete specification of the system stored in Git. It acts as the blueprint from which the actual state is continuously reconciled, ensuring the system remains consistent and reproducible.''

Thus, the primary purpose of Desired State is to act as a blueprint to recreate and ensure consistency of the system.

===========

Question 5

When using Kustomize, how are resources, configurations, and customizations commonly organized?

ABy specifying all resources inline in the customization file.

BIn separate configuration files for each resource.

CIn a single configuration file.

DUsing a combination of folder directories and referenced folder/file paths.

Answer : D

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.

===========

Question 6

In the context of GitOps, why would you do a rollback?

ATo undo a deployment that introduced a critical bug or caused a system failure.

BTo improve performance and optimize resource utilization.

CTo create a backup of the current configuration.

DTo test a new feature in a controlled environment.

Answer : A

In GitOps, rollback is the process of reverting to a previous known-good configuration stored in Git. This is typically done when a deployment introduces a bug, error, or failure that impacts system stability.

''Rollback in GitOps is used to revert to a previous commit representing a stable configuration when the current deployment causes errors or failures.''

Thus, the correct answer is A.

Question 7

In GitOps, what is a pull-based approach?

AA pull-based approach is when developers manually push changes to the GitOps system, which then applies them automatically.

BA pull-based approach is when the GitOps system sends notifications to developers to apply changes from the Git repository manually.

CA pull-based approach is when the Git repository automatically pushes changes to the GitOps system, which then applies them.

DA pull-based approach is when the GitOps system continuously polls the Git repository for changes and applies them automatically.

Answer : 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.

Linux Foundation Certified GitOps Associate CGOA Exam Practice Test