CGOA Practice Test 8 — 10 Questions

Question 1

Which term best describes the process of ensuring the live cluster matches the desired state stored in Git?

Accepted Answer

Syncing. Syncing is the GitOps term for the process of applying the desired state from Git to the live cluster so that the actual state matches the declared state. In Argo CD, a sync operation applies manifests; in Flux, reconciliation achieves the same. The question describes exactly this convergence process, making 'Syncing' the correct term.

Answer

Validation

Answer

Provisioning

Answer

Compilation

Question 2

Which TWO are examples of 'Drift' in a GitOps environment?

Accepted Answer

A manual update to a Deployment image via kubectl.. In GitOps, drift is any divergence between the desired state stored in Git and the actual state running in the cluster. Option B is correct because running kubectl to change a Deployment's image modifies the live cluster state outside of Git, so the actual state no longer matches the declared manifest, which is classic configuration drift. Option E is correct because editing a Service type directly in the cluster (e.g., changing ClusterIP to NodePort) also bypasses Git and creates a mismatch between the declared and observed state. Option A is not drift because a CPU spike is a transient runtime metric, not a configuration divergence from Git. Option C is not drift because a container crash is an application/runtime failure, not a change to the declared desired state. Option D is not drift because a new Git commit updates the desired state itself and is the normal GitOps change mechanism, not a divergence from it.

Answer

A temporary spike in CPU usage.

Answer

A container crashing due to a code bug.

Answer

A new Git commit.

Question 3

Which TWO of the following are features of progressive delivery in GitOps? (Select two)

Accepted Answer

Gradual traffic shifting between application versions.. Option A is correct because progressive delivery in GitOps is fundamentally about gradually shifting traffic between application versions—using techniques like canary releases or blue-green deployments—so that a new version receives only a small percentage of traffic initially and that share increases as confidence grows. Option C is correct because progressive delivery tightly couples traffic shifting with automated analysis of custom metrics (e.g., error rate, latency, or business KPIs); if those metrics breach defined thresholds, the rollout is automatically rolled back, which is a core GitOps progressive delivery capability. Option B is not a feature of progressive delivery—manually logging into pods is an ad-hoc, non-automated troubleshooting step that contradicts the automated, declarative nature of GitOps. Option D is incorrect because immediate deployment of all changes to the entire cluster is a big-bang release, the opposite of progressive delivery's incremental rollout. Option E is incorrect because removing health checks would eliminate the very signals progressive delivery relies on to validate a rollout and trigger automated rollback.

Answer

Manually logging into pods to check health.

Answer

Immediate deployment of all changes to the entire cluster.

Answer

Removing all health checks from the application.

Question 4

Which TWO of the following are valid strategies for promoting an application from staging to production in GitOps? (Select two)

Accepted Answer

Merging a pull request from a staging branch to a production branch.. Option C is correct because in GitOps the Git repository is the single source of truth, so promoting an application is done by merging a pull request from a staging branch into a production branch, which changes the desired state that the GitOps operator (e.g., Argo CD or Flux) then reconciles into the production cluster. Option E is correct because GitOps commonly uses a directory-per-environment layout (e.g., kustomize overlays or Helm values files), so updating the environment-specific values file in the production directory commits the new desired production configuration, which the GitOps controller detects and applies. Option A is not a valid promotion strategy because deleting and recreating the application discards state and is not a declarative Git-driven promotion. Option B is not valid because 'kubectl rollout undo' is an imperative manual rollback that bypasses Git and would be reverted by the GitOps reconciler. Option D is not valid because pushing directly to the cluster bypasses the CI/CD pipeline and Git, violating the core GitOps principle that all changes flow through Git.

Answer

Deleting the application and recreating it.

Answer

Running a 'kubectl rollout undo' command manually.

Answer

Bypassing the CI/CD pipeline by pushing directly to the cluster.

Question 5

In GitOps, what is the 'Source of Truth'?

Accepted Answer

The Git repository.. In GitOps, the Git repository is the single source of truth because it holds the declarative manifests that define the desired state of the entire system. All changes originate as commits, and the GitOps agent continuously reconciles the live cluster to match what is declared in Git. This makes Git the authoritative record, not the running cluster.

Answer

The running Kubernetes cluster.

Answer

The CI pipeline logs.

Answer

The container registry.

Question 6

Which of these is a valid 'GitOps' approach for multi-environment management?

Accepted Answer

Using separate directories or branches for different environments (e.g., /overlays/prod).. GitOps relies on declarative infrastructure stored in Git, and using separate directories or branches for each environment (e.g., /overlays/prod) is a standard pattern to manage multi-environment configurations. This approach allows environment-specific customizations (like replicas, resource limits, or image tags) while keeping the base configuration DRY, often implemented with tools like Kustomize or Helm. It also enables independent promotion and rollback per environment via Git commits.

Answer

Ignoring environments and deploying everything to one namespace.

Answer

Using a single folder for all environments and using a script to toggle them.

Answer

Deploying directly to production using kubectl.

Question 7

You are using Kustomize 'overlays' for environment promotion. If you need to add a specific label to all resources in production but not in staging, where should you define it?

Accepted Answer

In the 'overlays/production' kustomization.yaml file.. In Kustomize, overlays are used to customize base resources for different environments. To add a label only in production, you define it in the production overlay's kustomization.yaml using the 'commonLabels' or 'labels' field. This ensures the label is applied only to resources in that overlay.

Answer

In the global GitOps config map.

Answer

By modifying the manifest manually after deployment.

Answer

In the 'base' directory kustomization.yaml file.

Question 8

What is the primary benefit of version controlling your cluster manifests?

Accepted Answer

It allows you to track, audit, and revert cluster changes. Version controlling cluster manifests (e.g., YAML files for Kubernetes resources) provides a historical record of every change made to the desired state of the cluster. This enables tracking who changed what and when, auditing for compliance or troubleshooting, and reverting to a previous working state if a change causes issues. These capabilities are core to GitOps and infrastructure-as-code practices, where the manifest repository is the single source of truth for cluster configuration.

Answer

It allows you to host files on your local desktop

Answer

It replaces the need for a database

Answer

It speeds up node startup time

Question 9

An organization uses Argo CD to manage Kubernetes clusters. A developer manually modifies a Deployment's replica count via kubectl. Which mechanism in Argo CD ensures this manual change is identified as non-compliant with the GitOps repository?

Accepted Answer

Argo CD Application Controller's reconciliation loop. Argo CD's Application Controller runs a continuous reconciliation loop that periodically compares the desired state in Git with the live state in the cluster. When a developer manually changes a Deployment's replica count via kubectl, the controller detects the difference (OutOfSync) and, if auto-sync with self-heal is enabled, reverts the live resource to match Git. This is the core drift-detection mechanism in Argo CD.

Answer

Git repository webhook

Answer

Kubernetes admission controllers

Answer

Kubernetes Garbage Collector

Question 10

Which action should a developer take to deploy a new version of an application in a GitOps-based workflow?

Accepted Answer

Submit a pull request to the Git repository containing the configuration update.. In a GitOps workflow, Git is the single source of truth, so any change to application state — including a new version — must be expressed as a commit or pull request to the configuration repository. The CD controller then detects the change and reconciles the cluster. This makes the PR the correct deployment trigger, providing review, audit trail, and rollback via Git history.

Answer

Wait for the automated CI/CD tool to trigger a redeployment.

Answer

Run 'kubectl apply' from their local machine.

Answer

Log into the Argo CD dashboard and click 'Deploy'.