CGOA Practice Test 6 — 10 Questions

Question 1

When a manual change is made directly to a Kubernetes Service via 'kubectl edit', what behavior is expected from a properly configured GitOps operator set to 'Automatic Sync'?

Accepted Answer

The operator identifies the drift and automatically overwrites the live state with the Git version.. With Automatic Sync enabled, a GitOps operator such as Argo CD continuously compares live cluster state against the desired state in Git. When it detects drift — for example, a manual kubectl edit to a Service — it automatically re-applies the Git version, overwriting the manual change. This self-healing behaviour is the core guarantee of GitOps: Git remains the single source of truth.

Answer

The operator ignores the change to prevent production downtime.

Answer

The operator updates the Git repository to match the new manual change.

Answer

The operator prompts the administrator for manual approval before reverting.

Question 2

What is the purpose of the 'destination' field in an Argo CD Application manifest?

Accepted Answer

It defines the target Kubernetes cluster and namespace.. The destination field in an Argo CD Application manifest specifies the target Kubernetes cluster (by server URL or name) and the namespace where the application's resources will be deployed. It tells Argo CD where to apply the manifests from the source repository. This is essential for multi-cluster deployments.

Answer

It defines the sync frequency.

Answer

It defines the user who triggered the sync.

Answer

It defines the Git repository URL.

Question 3

You are debugging a GitOps deployment. The controller shows 'OutOfSync' but the cluster seems to be running correctly. What is the most likely cause?

Accepted Answer

Manual changes were made to the live resource that weren't captured in Git.. An 'OutOfSync' status means the live cluster state diverges from the desired state declared in Git. If the cluster is running correctly, the most common cause is that someone made manual changes (kubectl edit, kubectl apply, or a hotfix) directly to the live resource, so the controller detects drift between Git and the cluster. The controller is functioning as designed by flagging the discrepancy.

Answer

The network latency to the Git server is too high.

Answer

The Git repository is empty.

Answer

The controller is broken.

Question 4

Which of the following is considered 'best practice' for GitOps repository structure?

Accepted Answer

Using a separate repository for environment configurations. Best practice for GitOps repository structure is to separate application source code from deployment configuration, and often to use separate repositories (or at least separate directories) for environment-specific configurations (dev, staging, prod). This separation enables independent promotion, access control, and rollback per environment, and prevents a change to one environment from inadvertently affecting another. Using a separate repository for environment configurations is a recognized best practice.

Answer

Storing source code and manifest files in the same directory

Answer

Keeping all configuration in a single root file

Answer

Committing binary files to the repo

Question 5

Which THREE are standard ways to implement GitOps with Helm?

Accepted Answer

Using a GitOps operator to trigger 'helm install'.. Option C is correct because GitOps operators such as Argo CD or Flux watch a Git repository and automatically trigger Helm operations like 'helm install' or 'helm upgrade' when the desired state changes, which is the core GitOps reconciliation loop. Option D is correct because storing the final rendered YAML manifests in Git is a valid GitOps pattern (often called 'rendered manifests' or 'last-mile' GitOps), where the cluster state is applied directly from committed YAML without Helm running in the cluster. Option E is correct because storing Helm values files in Git is a standard GitOps approach where the chart is referenced from a chart repository and the environment-specific values are version-controlled, allowing the operator to render and apply the release. Option A is not a GitOps implementation because running 'helm upgrade' manually is an imperative, human-driven action that bypasses Git as the single source of truth. Option B is not a complete GitOps implementation because storing only the chart source code without values, rendered manifests, or an automated operator does not provide the declarative, continuously reconciled deployment that GitOps requires.

Answer

Running 'helm upgrade' manually.

Answer

Only storing the chart source code.

Question 6

When managing multiple environments (dev/stage/prod) in one repository, which folder structure is generally considered best practice?

Accepted Answer

Using environment-specific folders.. Environment-specific folders (e.g., /dev, /stage, /prod) keep manifests for each environment isolated while sharing a single repository, enabling consistent promotion workflows and clear ownership. This structure lets GitOps tools like Argo CD or Flux target a specific path per environment without duplicating the entire repo. It also makes diffs between environments obvious and supports per-environment overlays (Kustomize) or values files (Helm).

Answer

Storing configurations in the application code folder.

Answer

Putting everything in a single root folder.

Answer

Using different Git repos for every single manifest.

Question 7

Which Argo CD feature allows you to manage multiple applications with shared configuration?

Accepted Answer

ApplicationSets.. ApplicationSets is the Argo CD controller that generates multiple Application resources from a single template combined with generators (List, Cluster, Git, Matrix, Merge, Pull Request). It is purpose-built for managing many applications that share configuration, such as one app per cluster or per tenant.

Answer

Sync Waves.

Answer

Application Projects.

Answer

Resource Hooks.

Question 8

Which of the following is NOT a benefit of the GitOps model?

Accepted Answer

Increased system performance.. GitOps is a deployment and operational model that uses Git as the single source of truth for declarative infrastructure and applications. Its primary benefits are improved auditability (every change is a Git commit), faster disaster recovery (the desired state can be reapplied from Git), and standardized deployment processes (consistent workflows across environments). Increased system performance is not a benefit of GitOps; performance depends on application design, resource allocation, and infrastructure, not on how deployments are managed.

Answer

Improved auditability.

Answer

Faster recovery from disasters.

Answer

Standardized deployment processes.

Question 9

In a GitOps environment using Argo CD, what is the primary purpose of the reconciliation loop?

Accepted Answer

To automatically apply changes from the Git repository to the target Kubernetes cluster.. Argo CD's reconciliation loop continuously compares the desired state in Git with the live state in the cluster and, when auto-sync is enabled, applies the differences to bring the cluster into the desired state. This is the core mechanism that makes Git the source of truth for deployments.

Answer

To perform unit testing on manifest files before they are merged.

Answer

To push new container images to the registry whenever a build completes.

Answer

To scale deployment replicas based on real-time traffic metrics.

Question 10

In a GitOps pattern, how do you manage a rollback when an application deployment fails?

Accepted Answer

Revert the commit in Git and let the GitOps operator reconcile.. In GitOps, Git is the single source of truth for the desired state of the system. To roll back a failed deployment, you revert the offending commit in Git, which changes the desired state back to the last known good version. The GitOps operator (e.g., Argo CD or Flux) continuously reconciles the cluster to match Git, so it will automatically apply the rollback. This approach ensures that the rollback is version-controlled, auditable, and consistent with the declarative model.

Answer

Delete the pods and let the operator recreate them.

Answer

Stop the GitOps operator to prevent it from correcting the state.

Answer

Run 'kubectl rollout undo' on the deployment.