CGOA Gitops Terminology Practice Test 4 — 15 Questions

Question 1

Which of the following is a potential downside of using a 'Pull' model?

Accepted Answer

It requires maintaining an operator within the cluster. In a Pull model, the GitOps agent (operator) runs inside the cluster and continuously pulls desired state from Git. This means an operator must be deployed, maintained, upgraded, and monitored within each cluster, adding operational overhead. The agent also needs RBAC permissions to apply changes, and its lifecycle must be managed alongside the workloads it controls.

Answer

It requires public IP addresses

Answer

It is slower than pushing

Answer

It creates a security hole

Question 2

What happens when a resource's 'SyncPolicy' is set to 'Manual'?

Accepted Answer

The operator will report 'OutOfSync' until a human triggers the sync. When SyncPolicy is set to Manual, the GitOps operator still watches the repository and computes the diff between desired and live state, but it does not apply changes automatically. As soon as a difference is detected, the application is marked OutOfSync, and it remains in that state until a human explicitly triggers a sync (e.g., via the UI, CLI, or API). This gives operators control over when changes hit the cluster, which is useful for production environments requiring approval gates.

Answer

The operator will delete the resource

Answer

The operator will stop watching the repository

Answer

The operator will automatically sync as soon as a change is detected

Question 3

Which THREE of the following represent key concepts in 'GitOps'?

Accepted Answer

Infrastructure as Code (IaC). Option A (Infrastructure as Code) is correct because GitOps requires all infrastructure and application configuration to be expressed declaratively in code, so it can be versioned and stored in Git rather than configured manually. Option D (Automated Reconciliation) is correct because a GitOps agent (e.g., Argo CD or Flux) continuously compares the live cluster state against the desired state in Git and automatically converges the system to that desired state. Option E (Git as the Source of Truth) is correct because in GitOps the Git repository is the single authoritative source for the desired state of the system, and all changes flow through Git commits and pull requests. Option B (Manual intervention for every change) is not a GitOps concept, since GitOps emphasizes automated, declarative deployments triggered by Git changes rather than manual steps. Option C (Direct terminal access to production) is also not a GitOps concept, as GitOps discourages direct imperative access to production in favor of changes made through Git and applied by the reconciliation controller.

Answer

Manual intervention for every change

Answer

Direct terminal access to production

Question 4

What does the status 'Healthy' mean in an Argo CD application?

Accepted Answer

The application is running as expected in the cluster. In Argo CD, the 'Healthy' status is a health assessment of the live Kubernetes resources that make up an application. It means that all resources are in a healthy state according to their health checks—for example, Deployments have all replicas available, Pods are Running and Ready, and Services have endpoints. This indicates the application is running as expected in the cluster, not merely that Git is synced or that infrastructure components like network or database backups are in place.

Answer

The network is secure

Answer

The database is fully backed up

Answer

The Git repository is updated

Question 5

Which TWO of the following are NOT recommended in a GitOps workflow?

Accepted Answer

Manual changes via kubectl. Option B (Manual changes via kubectl) is NOT recommended in a GitOps workflow because GitOps requires the Git repository to be the single source of truth, and any out-of-band change made directly with kubectl creates configuration drift that the reconciliation controller will detect and revert, defeating the declarative model. Option C (Storing plain-text secrets in the repository) is NOT recommended because committing unencrypted credentials to Git exposes sensitive data to anyone with repository access and to the permanent Git history, violating security best practices; secrets should instead be managed with tools like Sealed Secrets, SOPS, or an external vault. By contrast, option A (Automated reconciliation of state) is a core GitOps principle, typically implemented by controllers such as Argo CD or Flux continuously comparing live cluster state to the desired state in Git. Option D (Using Git as a source of truth) is the foundational GitOps tenet, providing versioning, auditability, and rollback. Option E (Using pull requests for code changes) is recommended because it enables peer review, CI validation, and an auditable approval trail before changes are merged and deployed.

Answer

Automated reconciliation of state

Answer

Using Git as a source of truth

Answer

Using pull requests for code changes

Question 6

What is the purpose of a 'Sync Window' in Argo CD?

Accepted Answer

To limit when automated syncs occur. A Sync Window in Argo CD restricts automated syncs to defined time ranges, preventing deployments during sensitive periods such as business hours, change freezes, or peak traffic. It is configured with a schedule (cron-like), duration, and optional time zone, and applies to Applications via selectors.

Answer

To increase the size of the Git repo

Answer

To prevent users from logging in

Answer

To optimize network speed

Question 7

What is the impact of having multiple GitOps operators in the same cluster?

Accepted Answer

It leads to potential race conditions and configuration conflicts. Running multiple GitOps operators (e.g., two Argo CD instances or Argo CD plus Flux) against the same cluster means each operator independently reconciles resources toward its own declared desired state. When both manage overlapping resources, they will continuously overwrite each other's changes, producing race conditions, flapping resource states, and configuration conflicts. GitOps assumes a single source of truth per resource, so multiple controllers violate that model rather than improving it.

Answer

It is the recommended setup for high availability

Answer

It automatically distributes the load across nodes

Answer

It increases the throughput of deployments

Question 8

What is an 'Image Updater' in the GitOps ecosystem?

Accepted Answer

A controller that updates image tags in Git. An Image Updater in GitOps is a controller that monitors container registries for new image versions and automatically updates the corresponding image tags in Git repositories. This ensures that the desired state in Git reflects the latest available images, enabling automated deployments through GitOps workflows. Tools like Argo CD Image Updater and Flux's Image Automation Controller implement this pattern by committing changes to Git, which are then synced to the cluster.

Answer

A tool to compress images

Answer

A tool to clean up old images in the registry

Answer

A tool to scan images for vulnerabilities

Question 9

How do you handle 'Environment-specific' configurations in a GitOps repository?

Accepted Answer

By using overlays or templating tools. Environment-specific configurations in GitOps are best handled with overlays or templating tools such as Kustomize overlays or Helm values files. These allow a single base configuration to be customized per environment (dev, staging, prod) without duplicating manifests, keeping the repository DRY and maintainable while preserving a single source of truth.

Answer

By creating separate branches for each environment

Answer

By having multiple Git repositories per cluster

Answer

By hardcoding the environment in the application

Question 10

Which THREE of the following are benefits of using a GitOps operator for CD?

Accepted Answer

Continuous synchronization of desired state. Option B is correct because a GitOps operator such as Argo CD or Flux continuously reconciles the live cluster state against the desired state declared in Git, automatically applying changes when the repository is updated. Option C is correct because the operator continuously compares actual versus desired state and surfaces any drift through its status, health, and diff views, giving teams clear visibility into configuration divergence. Option D is correct because the operator runs inside the cluster and pulls manifests directly from Git, so the external CI system no longer needs long-lived cluster credentials to push deployments, reducing the credential attack surface. Option A is not a core benefit of a GitOps operator, since environment creation is typically handled by IaC tooling or platform templates rather than the CD reconciler itself. Option E is incorrect because GitOps operators do not require manual approval on every sync; they are designed for automated reconciliation, with manual gates being optional and configurable.

Answer

Automatic creation of development environments

Answer

Requirement for manual approvals on every sync

Question 11

Which GitOps tool is primarily associated with the 'pull' deployment model?

Accepted Answer

Flux. Flux is a CNCF-graduated GitOps operator that implements the pull model: an in-cluster agent watches Git repositories and pulls changes into the cluster, rather than an external system pushing deployments in. This pull architecture is the defining characteristic of modern GitOps tooling and is why Flux (alongside Argo CD) is the canonical example.

Answer

Jenkins

Answer

Ansible

Answer

Terraform

Question 12

What is the difference between a 'Sync' and a 'Refresh' in Argo CD?

Accepted Answer

Refresh updates the application status; Sync applies changes to the cluster. In Argo CD, 'Refresh' is a read-only operation that re-queries the Git repository and the live cluster to update the application's status, diff, and sync state without modifying anything. 'Sync' is the write operation that applies the desired manifests from Git to the target Kubernetes cluster, bringing live state into alignment with the declared state. The two are distinct phases: Refresh detects drift, Sync remediates it.

Answer

Sync is for reading; Refresh is for writing

Answer

Refresh is for Git; Sync is for the cloud provider API

Answer

They are the same thing

Question 13

What is the primary role of a 'GitOps controller'?

Accepted Answer

To watch the repository and reconcile the cluster state. A GitOps controller (e.g., Argo CD's application controller or Flux's kustomize-controller) continuously watches the Git repository for the desired state and reconciles the live cluster to match it, detecting and correcting drift. It is the engine that closes the loop between declarative intent in Git and actual cluster state. Without it, GitOps is just version-controlled YAML with no enforcement.

Answer

To host the container registry

Answer

To generate user tokens

Answer

To manage Git branches

Question 14

What happens if the Git repository is temporarily unavailable during a sync cycle?

Accepted Answer

The operator waits and retries the fetch. GitOps operators such as Argo CD or Flux are designed to be resilient to transient failures. When the Git repository is temporarily unreachable, the operator does not alter the cluster; it simply waits and retries the fetch on its next reconciliation loop, preserving the last known desired state. This ensures the cluster remains stable and avoids destructive actions caused by a temporary network or repository outage.

Answer

The operator wipes the current state

Answer

The cluster reverts to a hardcoded default

Answer

The cluster automatically deletes all applications

Question 15

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.