Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
In GitOps, what does the principle of Versioned and Immutable mean?
One of the four fundamental GitOps principles is Versioned and Immutable. This means that the entire system's desired state must be stored in a Git repository with version control. Each change must be represented as a commit, and Git's immutability guarantees a reliable, auditable history of how the system evolved.
''The desired state is stored in a version control system. The record of truth is stored in an immutable history, and changes can be audited and reverted if necessary. This guarantees that the system's configuration is versioned, immutable, and traceable.''
Thus, configuration and infrastructure must be version-controlled and immutable, never changed directly in production.
Which of the following is an example of an external reconciler?
A reconciler ensures that the actual system matches the desired state declared in Git. External reconcilers run outside the core cluster orchestration process. Flux is 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: Flux is correct.
In the context of GitOps, what is the purpose of a State Store?
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.
You want to create a dashboard to monitor the performance of your application. Which of the following is a key principle of GitOps regarding dashboards?
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, D is correct.
You want to route alerts from Prometheus to Slack in your GitOps workflow. Which tool can you use to achieve this?
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.
60 questions covering all exam domains, starting from $20
Exam domains verified against: Official Linux Foundation CGOA exam guide, last checked September 2026.
Understand the core vocabulary and concepts that define GitOps systems. This covers declarative descriptions of desired state, state drift, reconciliation processes, state stores, feedback loops, and rollback capabilities that form the foundation of GitOps practice.
Master the four core principles that define GitOps: systems must be declared, versions stored immutably, changes pulled automatically, and state continuously reconciled. These principles guide how you design and operate GitOps managed systems.
Connect GitOps to adjacent operational practices including Configuration as Code, Infrastructure as Code, DevOps and DevSecOps approaches, and CI and CD pipelines. Understanding how these practices complement and enable GitOps is essential.
Learn deployment and release patterns, progressive delivery approaches, pull-based versus event-driven reconciliation, and architectural patterns for both in-cluster and external reconcilers. These patterns show you how to implement GitOps in real systems.
Sample question from this domain above: Q4
Explore how to work with manifest formats and packaging, state store systems like Git and alternatives, reconciliation engines such as ArgoCD and Flux, and how these tools integrate with notifications, observability, and continuous integration systems.
Common questions about the exam itself
