Linux Foundation CGOA Exam Questions Instant Access

Question 1

Which method(s) of accessing the Desired State store does GitOps support?

APush method only

BReplication only

CNeither push nor pull

DPull is required and push can optionally be used in addition to pull

Answer : D

GitOps requires a pull-based approach as 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 is D.

===========

Question 2

In GitOps, which option describes State Store management?

AStoring state information in a relational database.

BStoring state information in a centralized database.

CStoring state information in a distributed file system.

DStoring state information in a version control system.

Answer : D

The State Store is typically implemented using a version 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 is D: version control system.

Question 3

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 4

In the context of GitOps, what is the purpose of a State Store?

ATo provide a system for storing temporary state data during GitOps deployments.

BTo provide a system for storing mutable versions of Desired State declarations.

CTo provide a system for storing the current state of an application.

DTo provide a system for storing immutable versions of Desired State declarations.

Answer : D

A State Store in GitOps is the system of record where Desired State declarations are kept. It must be immutable and versioned to ensure full auditability, traceability, and rollback capabilities. Git itself is the most common State Store.

''The Desired State must be stored in a State Store that is versioned and immutable. This guarantees traceability and enables recovery by reverting to previous commits.''

Thus, the correct answer is D.

===========

Question 5

How do you ensure that you are achieving the Pulled Automatically GitOps principle?

ABy deploying changes from the version control repository by applying them through an automated pipeline when major updates are needed.

BBy having an operator continuously monitor and pull changes from the source of truth.

CBy maintaining multiple Git repositories for different aspects of your infrastructure and applications.

DBy manually triggering deployments and configurations using scripts and commands.

Answer : B

The Pulled Automatically principle in GitOps means that agents inside the runtime environment (e.g., controllers/operators) continuously monitor Git (the source of truth) and automatically pull changes when updates are detected.

''Software agents continuously pull changes from the version control system and reconcile them automatically. This pull-based approach ensures automation, security, and self-healing.''

Thus, the correct answer is B.

Question 6

You want to route alerts from Prometheus to Slack in your GitOps workflow. Which tool can you use to achieve this?

AAlertmanager

BSlack

CPrometheus

DJenkins X

Answer : A

Prometheus is commonly used in GitOps for monitoring. Alertmanager is the tool integrated with Prometheus to handle alert routing. It supports sending alerts to external systems such as Slack, PagerDuty, or email.

''Prometheus generates alerts, which are routed and managed by Alertmanager. Alertmanager can integrate with messaging tools like Slack to deliver alerts in real time.''

Thus, the correct answer is A: Alertmanager.

===========

Question 7

In GitOps, what does it mean to Continuously Reconcile?

ARegularly update Git repositories with the latest changes from external sources.

BPerform regular backups of Git repositories.

CAutomatically compare and adjust the system state as needed.

DMonitor the system for any unauthorized changes and revert them.

Answer : C

Continuous reconciliation is 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 agent automatically reconciles the 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 provides automation, consistency, and self-healing, which are hallmarks of GitOps.

Linux Foundation Certified GitOps Associate CGOA Exam Questions