CGOA Gitops Terminology Practice Test 1 — 15 Questions

Question 1

Which THREE of the following are core responsibilities of a GitOps operator?

Accepted Answer

Detecting drift between the cluster state and the Git source. Operators are designed to observe, analyze, and act to reconcile differences.

Answer

Writing CI/CD build scripts

Answer

Executing manual kubectl commands for developers

Question 2

When setting up Argo CD, which TWO components are essential to define a GitOps workflow?

Accepted Answer

AppProject. An Application object defines the source and destination, and a Project organizes them.

Answer

Kubernetes Node

Answer

Docker Registry

Answer

Jenkins Pipeline

Question 3

You are troubleshooting a Flux installation. The operator is failing to pull updates from a private GitHub repository. What component is most likely misconfigured?

Accepted Answer

The GitRepository secret. Flux uses Kubernetes Secrets to store the SSH keys or tokens required for authentication with Git providers.

Answer

The Helm chart version

Answer

The cluster service account permissions

Answer

The Kustomization path

Question 4

A company transitions from a push-based CI/CD pipeline (using Jenkins) to a pull-based GitOps model (using Flux). What is the primary security architectural change regarding cluster access?

Accepted Answer

The CI server no longer requires cluster credentials. In push models, the CI server requires cluster credentials. In pull models, the operator inside the cluster initiates the fetch, removing the need for external cluster-admin access.

Answer

Git is no longer the source of truth

Answer

The cluster no longer requires an API server

Answer

The operator is now a push-based agent

Question 5

You are auditing your GitOps deployment strategy. Which TWO of the following statements correctly describe the 'Source of Truth' in a GitOps architecture?

Accepted Answer

The declared state in the Git repo must match the observed cluster state. The Git repository is the canonical state, and the cluster is a reflection of that state.

Answer

The live cluster state is the ultimate source of truth for all configurations

Answer

Database backups constitute the primary source of truth

Answer

Continuous Integration artifacts are the source of truth

Question 6

What is the primary benefit of a 'pull' deployment model compared to a 'push' model in GitOps?

Accepted Answer

Reduced need for inbound firewall access to the cluster. Pull-based models eliminate the need to open inbound firewall ports or expose credentials to external services.

Answer

Support for non-Kubernetes platforms

Answer

Elimination of Kubernetes manifests

Answer

Faster application builds

Question 7

You are configuring an Argo CD application. After a developer manually modifies a Kubernetes Service via kubectl, the application status changes to 'OutOfSync'. Which GitOps principle is this monitoring process specifically identifying?

Accepted Answer

Drift detection. The reconciliation loop continuously compares the live state with the desired state defined in Git, flagging manual changes as drift.

Answer

Rollback recovery

Answer

Image promotion

Answer

Webhook integration

Question 8

An administrator notices that the 'sync' status of an Argo CD application is 'Synced' but the health status is 'Degraded'. What does this indicate?

Accepted Answer

The application is correctly defined in Git but is failing at runtime. The desired state in Git has been successfully applied to the cluster, but the workloads (e.g., Pods) are failing to run correctly.

Answer

The Argo CD controller has crashed

Answer

The Git repository is unreachable

Answer

Git and the cluster state are mismatched

Question 9

Which THREE of the following represent common symptoms of 'drift' in a GitOps-managed cluster?

Accepted Answer

Unexpected changes to resource labels or annotations. Drift occurs when the runtime state deviates from the Git-stored state.

Answer

Successful CI pipeline execution

Answer

Git commit history being too long

Question 10

In a GitOps environment, what is the 'Reconciliation Loop' primarily responsible for?

Accepted Answer

Continuously ensuring the cluster state matches the Git repository. The loop calculates the difference between current and desired state and applies actions to minimize that difference.

Answer

Running unit tests on application code

Answer

Generating new Kubernetes manifests

Answer

Managing user authentication for the Git provider

Question 11

When a GitOps tool reports a 'Sync Error', what is the most likely cause?

Accepted Answer

The manifest contains invalid Kubernetes syntax. Sync errors often result from resource conflicts or permission issues when applying manifests.

Answer

The Git repository is deleted

Answer

The cluster has too many nodes

Answer

The network latency is high

Question 12

Which TWO of the following are benefits of using Git as the 'Source of Truth'?

Accepted Answer

Clear audit trail of who changed what and when. Git provides history, auditability, and collaboration features.

Answer

Automatic removal of unused cloud accounts

Answer

Increased reliance on manual terminal access

Answer

Faster CPU performance for applications

Question 13

What is the primary function of an 'Operator' in the context of GitOps?

Accepted Answer

Automating the reconciliation process within the cluster. An operator is a Kubernetes controller that manages the lifecycle of applications by reconciling state.

Answer

Hosting the Git repository

Answer

Writing application code

Answer

Executing SQL queries

Question 14

You are using Flux and need to ensure that specific resources are ignored by the reconciliation process. Which feature should you utilize?

Accepted Answer

Kustomization ignore annotations. Flux allows using annotations to mark resources as 'ignore' or 'skip' to prevent the operator from modifying them.

Answer

Namespace-level network policies

Answer

Git commit filtering

Answer

ClusterRoleBinding exclusions

Question 15

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

Accepted Answer

Syncing. Syncing or Reconciliation is the process of applying the Git-defined state to the cluster.

Answer

Validation

Answer

Provisioning

Answer

Compilation