CGOA Gitops Terminology Practice Test 2 — 15 Questions

Question 1

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

Accepted Answer

The manifest contains invalid Kubernetes syntax. A 'Sync Error' in a GitOps tool such as Argo CD or Flux means the operator successfully retrieved the desired state from Git but failed to apply it to the cluster. The most common root cause is that the manifest itself is invalid — malformed YAML, an unknown API version, a missing required field, or a schema violation that the Kubernetes API server rejects. Because the error surfaces during the apply/reconcile step rather than the fetch step, it points squarely at the manifest content rather than connectivity or infrastructure capacity.

Answer

The Git repository is deleted

Answer

The cluster has too many nodes

Answer

The network latency is high

Question 2

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. Option A is correct because Git records every commit with author identity, timestamp, and a cryptographic hash of the exact changes, giving an immutable, reviewable history of who changed what and when — the essence of an audit trail for a source of truth. Option B is correct because Git's versioned history lets you undo a bad change deterministically with commands like git revert (which creates a new commit that inverts a prior one) or git reset, enabling reliable rollback to a known-good state. Option C is wrong because Git is a version-control system for code and configuration, not a cloud IAM or account-lifecycle tool; it cannot detect or delete unused cloud accounts. Option D is wrong because Git reduces reliance on manual terminal access by providing a structured, reviewable workflow (commits, branches, pull requests) rather than encouraging ad-hoc manual changes. Option E is wrong because Git has no bearing on application CPU performance; it manages source history, not runtime compute resources.

Answer

Automatic removal of unused cloud accounts

Answer

Increased reliance on manual terminal access

Answer

Faster CPU performance for applications

Question 3

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

Accepted Answer

Automating the reconciliation process within the cluster. In GitOps, an Operator is a Kubernetes controller that extends the API with custom resources and continuously reconciles the cluster to match the declared desired state. It encodes operational knowledge — such as how to deploy, upgrade, back up, or failover an application — into software that runs inside the cluster. This automation of the reconciliation process is precisely what makes Operators central to GitOps workflows.

Answer

Hosting the Git repository

Answer

Writing application code

Answer

Executing SQL queries

Question 4

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 5

In a GitOps workflow, how does an operator handle a situation where a user manually deletes a resource that is defined in Git?

Accepted Answer

It automatically recreates the resource. A GitOps operator continuously reconciles live cluster state against the desired state declared in Git. If a resource defined in Git is manually deleted, the operator detects the drift during its next reconciliation cycle and recreates the resource to match Git. Git remains the authoritative source, so the deletion is treated as unauthorized drift to be corrected.

Answer

It creates an alert and waits for manual intervention

Answer

It updates the Git repository to reflect the deletion

Answer

It blocks all future deployments until a reset occurs

Question 6

Which THREE of the following are critical security considerations for a GitOps implementation?

Accepted Answer

Requiring GPG signing for commits. Option A is correct because requiring GPG signing for commits ensures that only authorized developers can push changes to the Git repository, which is the single source of truth in GitOps; unsigned or tampered commits could otherwise inject malicious manifests into the cluster. Option C is correct because implementing RBAC for the Git repository restricts who can read, write, or merge to the branches that the GitOps operator reconciles, preventing unauthorized changes that would be automatically deployed. Option D is correct because storing secrets in external stores like HashiCorp Vault keeps sensitive credentials out of Git, where they would be exposed in plaintext and replicated to every cluster that syncs the repository. Option B is not correct because hardcoded passwords in Kubernetes manifests are a security anti-pattern that leaks credentials into version control. Option E is not correct because granting the GitOps operator cluster-admin access by default violates least privilege and dramatically expands the blast radius of a compromised operator.

Answer

Using hardcoded passwords in Kubernetes manifests

Answer

Granting the GitOps operator cluster-admin access by default

Question 7

Which TWO of the following are common GitOps terminology used to describe the state of an application?

Accepted Answer

Desired State. In GitOps, the Desired State (B) is the declarative configuration stored in Git that defines how the application and its infrastructure should look, serving as the single source of truth that the GitOps operator continuously reconciles toward. The Live State (C), also called the observed or actual state, is the real-time condition of the running application and cluster as reported by the GitOps agent (e.g., Argo CD or Flux), which is compared against the desired state to detect drift. These two terms form the core reconciliation loop of GitOps: the controller drives the live state to match the desired state. The other options are not GitOps terminology: Temporary State (A), Future State (D), and Legacy State (E) are not standard terms used to describe application state in GitOps workflows.

Answer

Temporary State

Answer

Future State

Answer

Legacy State

Question 8

What does the 'prune' setting in a GitOps controller do?

Accepted Answer

Automatically deletes resources from the cluster that are no longer in Git. The prune setting in a GitOps controller instructs it to delete live cluster resources that are no longer declared in Git. When enabled, if a manifest is removed from the repository, the controller will remove the corresponding object from the cluster during the next sync, keeping the cluster an exact mirror of Git. Without pruning, deleted manifests leave orphaned resources running indefinitely, causing drift and resource leakage.

Answer

Removes unused Git branches

Answer

Trims logs to save disk space

Answer

Limits the number of replicas

Question 9

An application is configured with 'Automated Sync'. What happens when a developer merges a change to the main branch?

Accepted Answer

The operator pulls the new state and updates the cluster. With Automated Sync enabled, the GitOps operator continuously reconciles the desired state in Git with the live cluster state. When a developer merges a change to the main branch, the operator detects the new commit during its next reconciliation cycle, pulls the updated manifests, and applies them to the cluster automatically. This is the core value proposition of GitOps: merge to deploy, with no manual intervention required.

Answer

The operator waits for a manual override

Answer

The operator deletes the application

Answer

The cluster crashes

Question 10

What is the purpose of a 'Kustomization' resource in a GitOps workflow?

Accepted Answer

To dynamically customize and patch manifests for different environments. A Kustomization resource (from Kustomize) defines how to customize and patch a set of base Kubernetes manifests for different environments — for example, overlaying a production replica count, image tag, or ConfigMap without duplicating YAML. It specifies resources, patches, name prefixes, and common labels, and is consumed natively by kubectl -k and by Argo CD/Flux. This makes it a core tool for environment-specific configuration in GitOps.

Answer

To perform load testing on the API server

Answer

To provide a secure shell into pods

Answer

To manage database migrations

Question 11

Which THREE of the following are potential risks of ignoring drift in a GitOps environment?

Accepted Answer

The Git repo becomes outdated relative to the cluster. Option B is correct because when drift occurs, manual changes are made directly to the cluster and never reflected back into Git, so the Git repository no longer represents the actual desired state and becomes outdated relative to the running cluster. Option C is correct because unmanaged manual changes can introduce unexpected configuration that conflicts with the declared manifests, leading to application instability, inconsistent behavior, or failed reconciliations. Option D is correct because manual changes bypass the reviewed, version-controlled Git workflow, so security-relevant settings (e.g., exposed ports, weakened RBAC, disabled TLS) can be introduced without audit or approval, creating unmanaged vulnerabilities. Option A is incorrect because ignoring drift does not reduce storage usage; drift typically adds untracked resources rather than freeing space. Option E is incorrect because ignoring drift does not increase deployment speed; it undermines the automated, reliable GitOps pipeline and often causes slower, error-prone remediation.

Answer

Reduced storage usage

Answer

Increased deployment speed

Question 12

When using an 'Image Updater' with a GitOps operator, what is the automated workflow?

Accepted Answer

It detects new images and updates the manifest in Git. An Image Updater (such as Argo CD Image Updater) monitors a container registry for new image tags and, when it detects a newer version matching the configured policy, writes the updated image tag back into the Git manifest. This keeps Git as the source of truth while automating image version bumps. The GitOps operator then syncs the updated manifest to the cluster.

Answer

It manually restarts the cluster

Answer

It creates a backup of the cluster

Answer

It bypasses the git repository entirely

Question 13

If you want to view the history of changes made to your cluster configuration, where should you look in a GitOps model?

Accepted Answer

The Git repository commit history. In a GitOps model, Git is the single source of truth for the desired state of the cluster, so the commit history of the Git repository is the authoritative audit trail of every configuration change. Each commit records who changed what and when, and Argo CD or Flux ties deployed revisions back to specific commits. This is the core GitOps principle: the cluster's change history lives in version control, not in the cluster itself.

Answer

The cluster event logs

Answer

The developer's local workstation

Answer

The cloud provider billing dashboard

Question 14

Which TWO of the following are characteristics of a 'GitOps Operator'?

Accepted Answer

It runs inside the Kubernetes cluster. Option C is correct because a GitOps Operator is deployed as a controller inside the Kubernetes cluster, where it watches custom resources and continuously manages the desired state of the environment. Option E is correct because the core function of a GitOps Operator is to observe the live cluster state, compare it against the desired state declared in Git, and act to reconcile any drift automatically. Options A, B, and D are incorrect: a GitOps Operator is not merely an external monitoring tool, it does not generate application source code, and it does not require manual triggers for every update since reconciliation is continuous and automated.

Answer

It is a purely external monitoring tool

Answer

It generates application source code

Answer

It requires manual triggers for every update

Question 15

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