Question 1

When are progressive delivery patterns useful in software development and deployment?

Accepted Answer

C

Explanation: Progressive delivery is a GitOps pattern used to release software gradually, reducing risks associated with deploying new versions. Techniques such as canary releases, feature flags, and blue-green deployments allow teams to incrementally roll out changes, validate functionality with subsets of users, and minimize potential disruptions. “Progressive delivery builds on continuous delivery by enabling safer, incremental rollouts. This pattern reduces risk, improves reliability, enhances user experience, and allows for validation of features with a portion of users before wider release.” Therefore, progressive delivery is useful in multiple scenarios (not just one-time deployments or small teams), making option C correct. Reference: GitOps Patterns (CNCF GitOps Working Group), Progressive Delivery Patterns documentation. ===========

Question 2

You are deploying a new version of your application using the Blue-Green deployment pattern. What is a characteristic of the Blue-Green deployment pattern?

Accepted Answer

C

Explanation: In a Blue-Green deployment, two environments (Blue and Green) exist at the same time. The current version runs in one environment (Blue), and the new version is deployed to the other environment (Green). Traffic is switched to Green once the new version is validated. “Blue-Green deployments maintain two production environments. The new version is deployed alongside the old version, and once validated, traffic is switched from Blue to Green.” Thus, the correct answer is C. Reference: GitOps Patterns (CNCF GitOps Working Group), Progressive Delivery. ===========

Question 3

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

Accepted Answer

D

Explanation: 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. Reference: GitOps Principles (CNCF GitOps Working Group), Reconciliation Models. ===========

Question 4

In GitOps, how is the Desired State stored?

Accepted Answer

D

Explanation: The GitOps principle of Versioned and Immutable requires Desired State to be stored in a way that enforces immutability 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 is D. Reference: GitOps Principles (CNCF GitOps Working Group). ===========

Question 5

In a GitOps-managed workflow, what is the correct way to initiate rollback?

Accepted Answer

B

Explanation: In GitOps, rollback is handled via version control. However, the practice is not to overwrite history but to roll forward by creating a new version that reverts to the configuration of a previous known- good commit. This maintains immutability and a complete audit trail. “With GitOps, changes are versioned immutably. Rollbacks are performed by rolling forward to a commit that represents a previous known-good configuration, ensuring history is preserved.” Thus, the correct GitOps approach is B. Reference: GitOps Principles (CNCF GitOps Working Group), Rollback and Recovery Practices. ===========

Question 6

Which of these is an advantage of using a declarative configuration for your Desired State?

Accepted Answer

B

Explanation: Declarative configuration describes what the system should look like, not how to achieve it. This enables the use of standard reconciliation tools (like ArgoCD or Flux) to manage the system automatically, removing the burden of writing and maintaining imperative scripts. “Declarative configuration enables systems to be managed by generic reconciliation tools rather than bespoke scripts, reducing operational overhead and increasing reliability.” Thus, the correct answer is B. Reference: GitOps Principles (CNCF GitOps Working Group), Declarative Systems. ===========

Question 7

You are packaging a complex application to deploy to multiple Kubernetes clusters using GitOps. Which of the following would be a suitable solution for this process?

Accepted Answer

A

Explanation: Helm is a Kubernetes package manager widely used in GitOps for packaging, configuring, and deploying complex applications. Helm charts bundle configuration, dependencies, and Kubernetes manifests into reusable, declarative packages that can be applied across multiple clusters. “Helm charts provide a way to package Kubernetes applications, defining configuration and dependencies declaratively. This allows consistent deployment across clusters in GitOps workflows.” Thus, the correct answer is A. Reference: GitOps Tooling (CNCF GitOps Working Group), Helm usage in GitOps. ===========

Question 8

A GitOps project wants to leverage both ArgoCD and Flux for a deployment. Can ArgoCD and Flux be used in conjunction?

Accepted Answer

C

Explanation: ArgoCD and Flux are the two primary CNCF GitOps tools. While both are reconciliation engines, they can be used together carefully if configured properly to avoid conflicts. For example, Flux can be used to manage configuration sources, while ArgoCD handles application-level delivery. Extensions and integration points allow them to complement each other. “ArgoCD and Flux implement the GitOps reconciliation principle. Though they provide overlapping functionality, they can be integrated by carefully managing their scope. For instance, Flux can manage sources and Helm charts, while ArgoCD handles higher-level deployments. Extensions exist to allow cooperation without conflict.” Thus, the correct answer is C. Reference: GitOps Tooling (CNCF GitOps Working Group). ===========

Question 9

Which of the following statements best describes the relationship between DevOps and GitOps?

Accepted Answer

B

Explanation: GitOps is not a replacement for DevOps. Instead, it is an evolution and practical implementation of DevOps principles, using Git as the single source of truth and continuous reconciliation as the operational model. “GitOps builds on the foundation of DevOps by providing a framework to put its principles into practice. It leverages Git and declarative reconciliation to realize DevOps goals.” Thus, the best description of the relationship is B. Reference: GitOps Related Practices (CNCF GitOps Working Group).

Question 10

In the context of GitOps, what source of truth guides the continuous deployment process?

Accepted Answer

A

Explanation: The Desired State, stored in Git, is the ultimate source of truth in GitOps. It defines how the system should look and behave. Continuous deployment processes reconcile the actual cluster state against this Desired State. “In GitOps, the desired state kept in Git is the single source of truth. The reconciler ensures the actual state matches the desired state, guiding the continuous deployment process.” Thus, the correct answer is A. Reference: GitOps Terminology (CNCF GitOps Working Group). ===========

Question 11

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

Accepted Answer

B

Explanation: 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. Reference: GitOps Principles (CNCF GitOps Working Group), Principle 4: Continuously reconciled and pulled automatically.

Question 12

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

Accepted Answer

A

Explanation: 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. Reference: GitOps Tooling (CNCF GitOps Working Group), Monitoring and Alerting practices. ===========

Question 13

You are working on a GitOps project and want to ensure that the configuration files are written in a standardized format. What is the recommended way to ensure this?

Accepted Answer

C

Explanation: Linting tools are essential in GitOps practices for maintaining consistency, standardization, and quality in configuration files. Automated linters can validate YAML manifests, Helm charts, or Kustomize overlays for formatting and best practices. “Linters automate the enforcement of formatting and quality rules in declarative configuration files. They ensure standardized structure and reduce errors in GitOps workflows.” Thus, the correct answer is C. Reference: GitOps Related Practices (CNCF GitOps Working Group). ===========

Question 14

In GitOps, how are the Desired State declarations pulled from the source?

Accepted Answer

C

Explanation: A fundamental GitOps principle is that reconciliation is automated and continuous. Software agents (e.g., controllers like ArgoCD or Flux) continuously pull desired state declarations from Git repositories and reconcile them with the actual state. “Software agents automatically pull the desired state declarations from the source of truth and continuously reconcile the actual state to match.” Thus, the correct answer is C. Reference: GitOps Principles (CNCF GitOps Working Group), Principle 4: Continuously reconciled. ===========

Question 15

In GitOps practices, when does CD take part?

Accepted Answer

B

Explanation: 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. Reference: GitOps Principles (CNCF GitOps Working Group), GitOps Working Group Terminology & Principles documents.

Free Linux Foundation CGOA Actual Exam Questions