CGOA Gitops Principles Practice Test 2 — 15 Questions

Question 1

An application is failing because a developer accidentally edited a ConfigMap in the cluster directly. Which GitOps feature prevents this from recurring?

Accepted Answer

Continuous reconciliation.. Continuous reconciliation is the GitOps mechanism where an agent (Argo CD, Flux) running in the cluster continuously compares the live state against the desired state declared in Git and automatically reverts any drift. If a developer manually edits a ConfigMap, the reconciler detects the divergence on its next sync cycle and restores the Git-declared value, preventing the manual change from persisting. This is the defining GitOps control that enforces Git as the single source of truth and eliminates configuration drift.

Answer

Role-Based Access Control (RBAC).

Answer

External DNS.

Answer

CI/CD pipeline triggers.

Question 2

You need to ensure that no one can modify cluster resources manually. How can you implement this in a GitOps-mature organization?

Accepted Answer

Remove cluster-admin access from all users except the GitOps controller.. In a GitOps-mature organization, the GitOps controller is the only entity with write access to the cluster, and all changes flow through Git. Removing cluster-admin access from all users except the GitOps controller enforces this by preventing manual modifications, ensuring that the Git repository remains the single source of truth. This is a foundational security practice in GitOps.

Answer

Install a plugin that logs all kubectl commands.

Answer

Add a firewall rule to block kubectl.

Answer

Disable the Kubernetes API server.

Question 3

Which of the following best describes the 'Declarative' principle in GitOps?

Accepted Answer

Defining the target state in configuration files.. Declarative means you describe the desired end state in version-controlled configuration files (YAML/JSON/HCL), and a controller continuously reconciles reality to match it. You declare 'what' the system should look like, not 'how' to get there step by step. This is the foundation that makes Git the single source of truth in GitOps.

Answer

Using an interactive terminal to manage resources.

Answer

Providing a script to update resources.

Answer

Requiring manual approval for every reconciliation.

Question 4

Your organization requires an audit trail of all changes to infrastructure. Why is GitOps superior to imperative 'kubectl' commands for this?

Accepted Answer

Git provides a permanent, immutable, and auditable history of who made what change and when.. GitOps uses Git as the single source of truth, so every change is a commit with author, timestamp, and diff. This creates a permanent, immutable, and auditable history of who changed what and when, which imperative kubectl commands do not provide.

Answer

Kubectl allows editing the live state without record.

Answer

Git is faster than kubectl for large clusters.

Answer

The cluster automatically emails admins when kubectl is used.

Question 5

When syncing a Git repository to a cluster, what is the 'Sync Policy' in Argo CD?

Accepted Answer

It defines whether the application should be synced automatically or manually.. The Sync Policy in Argo CD controls whether the application is synchronized automatically when Git changes are detected, or only when a user manually triggers a sync. It is configured via the `syncPolicy.automated` field in the Application manifest, and can include options like self-heal and prune. It does not manage credentials, health check frequency, or branch selection.

Answer

It sets the password for the Git repository.

Answer

It configures the frequency of the container health checks.

Answer

It determines which Git branch is used for the deployment.

Question 6

What is a 'GitOps Operator'?

Accepted Answer

A software agent that monitors Git and the cluster to maintain state alignment.. A GitOps operator is a software agent, such as Argo CD or Flux, that runs inside or alongside the cluster and continuously monitors both Git and the cluster to maintain state alignment. It reconciles the desired state defined in Git with the actual state in the cluster, automatically correcting drift. This agent-based reconciliation is the defining characteristic of GitOps.

Answer

A tool that converts YAML to JSON.

Answer

A database that stores configuration history.

Answer

A human user who manually pushes Git commits.

Question 7

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 8

Which of these is a typical 'Desired State' artifact in GitOps?

Accepted Answer

A Kubernetes YAML manifest.. In GitOps, the desired state is the declarative configuration that defines how the system should look. A Kubernetes YAML manifest is a canonical example: it declares resources like Deployments, Services, and ConfigMaps. This manifest is stored in Git and used by GitOps operators to reconcile the live cluster.

Answer

An audit log from the cluster.

Answer

A shell script that installs software.

Answer

A live running container.

Question 9

In a large enterprise, why is GitOps preferred for multi-cluster environments?

Accepted Answer

It allows a single source of truth to manage configuration consistency across all clusters.. GitOps uses a single Git repository as the source of truth for all cluster configurations, enabling consistent, version-controlled management across many clusters. This ensures configuration consistency and simplifies multi-cluster operations.

Answer

It enables developers to bypass security controls in dev clusters.

Answer

It automatically scales the nodes in all clusters.

Answer

It eliminates the need for any monitoring tools.

Question 10

Why does GitOps encourage the use of small, frequent commits?

Accepted Answer

To reduce the blast radius and simplify troubleshooting.. Small, frequent commits limit how many resources change in a single deployment, shrinking the blast radius if something breaks and making it easier to identify which commit introduced a problem. This aligns with GitOps principles of traceability and fast rollback via git revert.

Answer

To force developers to spend more time on documentation.

Answer

To ensure the Git server doesn't crash.

Answer

To minimize the size of the Git repository.

Question 11

When configuring a GitOps tool, what is the purpose of a 'webhook' in relation to the Git repository?

Accepted Answer

To trigger an immediate reconciliation attempt when a push occurs.. A webhook is an HTTP callback that the Git provider (GitHub, GitLab, Bitbucket) sends to the GitOps controller when events like a push occur. This lets the controller trigger an immediate reconciliation instead of waiting for its polling interval, cutting sync latency from minutes to seconds. It is an optimization, not a replacement for the controller's pull-based reconciliation.

Answer

To encrypt the traffic between the cluster and Git.

Answer

To replace the need for an SSH key.

Answer

To store the application images.

Question 12

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 13

What is the primary advantage of storing Kubernetes manifests in a version-controlled repository?

Accepted Answer

It provides a backup in case the cluster is deleted.. Storing Kubernetes manifests in a version-controlled repository (e.g., Git) creates a durable, auditable record of the desired cluster state. If the cluster is deleted or corrupted, the manifests can be re-applied to rebuild the environment, effectively acting as a backup of the declarative configuration. This is a core GitOps principle: Git is the single source of truth for both application and infrastructure definitions.

Answer

It makes the container images run faster.

Answer

It automatically patches security vulnerabilities.

Answer

It allows developers to bypass the CI/CD system.

Question 14

In GitOps, what does 'Self-Healing' mean?

Accepted Answer

The controller replaces manual changes with the state from Git.. Self-healing in GitOps means the controller continuously reconciles the live cluster state against the desired state in Git and automatically reverts any manual or out-of-band changes. If someone edits a Deployment with kubectl, the controller detects the drift and restores the Git-declared state.

Answer

The cluster reboots itself if it runs out of memory.

Answer

The application restarts if a pod crashes.

Answer

The developer re-pushes the code to fix the bug.

Question 15

When should you use Kustomize in a GitOps workflow?

Accepted Answer

To manage environment-specific overrides in a declarative way.. Kustomize is a declarative configuration customization tool that overlays environment-specific patches (replicas, image tags, resource limits, namespace) on top of a shared base without templating. In GitOps it is the standard way to keep one base and produce dev/staging/prod variants.

Answer

To build container images.

Answer

To delete all namespaces.

Answer

To perform load testing on the cluster.