CGOA Practice Questions

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.

===========

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.

===========

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.

===========

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).

===========

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.

===========

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.

===========

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.

===========

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).

===========

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).

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).

===========