CGOA Gitops Terminology Practice Test 2 — 15 Questions

Question 1

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. The reconciliation loop detects the absence of the resource and redeploys it to match the source of truth.

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 2

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

Accepted Answer

Requiring GPG signing for commits. Access control, secure credential storage, and commit signing are essential for security.

Answer

Using hardcoded passwords in Kubernetes manifests

Answer

Granting the GitOps operator cluster-admin access by default

Question 3

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

Accepted Answer

Desired State. 'Desired' vs 'Live' (or 'Current') are standard terms in GitOps.

Answer

Temporary State

Answer

Future State

Answer

Legacy State

Question 4

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

Accepted Answer

Automatically deletes resources from the cluster that are no longer in Git. Pruning ensures that resources not present in Git are removed from the cluster.

Answer

Removes unused Git branches

Answer

Trims logs to save disk space

Answer

Limits the number of replicas

Question 5

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. The controller detects the commit and immediately triggers a sync to update the cluster.

Answer

The operator waits for a manual override

Answer

The operator deletes the application

Answer

The cluster crashes

Question 6

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

Accepted Answer

To dynamically customize and patch manifests for different environments. Kustomization allows for templating and patching Kubernetes manifests for different environments without changing the base code.

Answer

To perform load testing on the API server

Answer

To provide a secure shell into pods

Answer

To manage database migrations

Question 7

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. Ignoring drift leads to configuration loss, security gaps, and deployment failures.

Answer

Reduced storage usage

Answer

Increased deployment speed

Question 8

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. The updater monitors registries for new images and updates the Git repository automatically.

Answer

It manually restarts the cluster

Answer

It creates a backup of the cluster

Answer

It bypasses the git repository entirely

Question 9

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. Because Git is the source of truth, the git log provides a complete history of all configuration changes.

Answer

The cluster event logs

Answer

The developer's local workstation

Answer

The cloud provider billing dashboard

Question 10

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

Accepted Answer

It runs inside the Kubernetes cluster. Operators run inside the cluster and act autonomously.

Answer

It is a purely external monitoring tool

Answer

It generates application source code

Answer

It requires manual triggers for every update

Question 11

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

Accepted Answer

Using a separate repository for environment configurations. Separating application code from infrastructure/environment configuration is a GitOps 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 12

Why is 'Git' used as the source of truth rather than a standard database?

Accepted Answer

Git provides native versioning, history, and collaboration. Git provides built-in version control, audit trails, and collaborative workflows that databases lack.

Answer

Git is the only format Kubernetes supports

Answer

Git is easier to host on-premise

Answer

Git is faster at read operations

Question 13

In an Argo CD 'Application' manifest, what does the 'destination' field specify?

Accepted Answer

The Kubernetes cluster and namespace for deployment. The destination defines the cluster URL and namespace where the resources should be deployed.

Answer

The source Git repository URL

Answer

The build server address

Answer

The email address for alerts

Question 14

Which THREE of the following are valid ways to trigger a sync in a GitOps environment?

Accepted Answer

Pushing a commit to the Git repository. Syncing can be manual, automated via commit, or triggered by a webhook.

Answer

Logging into the node via SSH

Answer

Restarting the Kubernetes API server

Question 15

What does the status 'OutOfSync' indicate in Argo CD?

Accepted Answer

The live resources are not identical to the Git manifests. It means the live state of the resources in the cluster does not match the desired state in the Git repository.

Answer

The Git repository is empty

Answer

The application is running out of memory

Answer

The Argo CD server is offline