CGOA Gitops Patterns Practice Test 2 — 15 Questions

Question 1

When configuring an App-of-Apps pattern, which field in the 'Application' manifest controls the order in which child applications are deployed?

Accepted Answer

argocd.argoproj.io/sync-wave. The 'syncPolicy.syncOptions' field, specifically 'ApplyOutOfSyncOnly=true' or using 'wave' annotations, manages deployment ordering. However, standard Argo CD 'syncWaves' are the primary mechanism for ordering resources within an app.

Answer

spec.project

Answer

spec.syncPolicy.automated.prune

Answer

spec.source.targetRevision

Question 2

You are troubleshooting a multi-cluster Argo CD deployment where the 'staging' cluster is healthy but 'production' cluster is 'OutOfSync' despite having the same manifest source. Why might this happen?

Accepted Answer

A manual 'kubectl apply' was performed on the production cluster.. Argo CD evaluates the state of the cluster against the Git definition. If a manual change or a different controller (like a Helm release) has altered the cluster state, the sync status will reflect a mismatch.

Answer

The production cluster has a newer version of the Kubernetes API.

Answer

The 'staging' cluster is using a different Argo CD instance.

Answer

The Git repo is only cloned to the staging cluster.

Question 3

Which mechanism is used in a GitOps workflow to ensure that a 'Canary' deployment successfully rolls back if error rates spike?

Accepted Answer

Flagger AnalysisTemplates.. Flagger monitors metrics via a provider (e.g., Prometheus) during the canary phase. If thresholds are exceeded, it automatically triggers a rollback to the previous version.

Answer

Kubernetes Liveness Probes.

Answer

Argo Rollouts 'pause' condition.

Answer

Git revert commands via CI/CD.

Question 4

Which of the following is a core principle of GitOps?

Accepted Answer

The system state is defined in a version-controlled repository.. GitOps defines the desired state in a version-controlled repository, which acts as the 'single source of truth'.

Answer

Manual intervention is required to scale deployments.

Answer

Developers should have direct 'cluster-admin' access.

Answer

The system state is defined by the latest CI pipeline execution.

Question 5

In a multi-cluster environment, you are managing resources across 50 clusters. Which pattern prevents the 'Control Plane' bottleneck?

Accepted Answer

ApplicationSets with Cluster Generators.. The 'Hub-and-Spoke' pattern with local agents (like Argo CD ApplicationSets or Flux controllers on each cluster) prevents a single central controller from having to manage thousands of API connections.

Answer

Storing all YAML in a single massive monorepo.

Answer

Manual kubectl context switching.

Answer

Centralized Cluster Management.

Question 6

What is the purpose of the 'destination' field in an Argo CD Application manifest?

Accepted Answer

It defines the target Kubernetes cluster and namespace.. The 'destination' field specifies the Kubernetes cluster (server) and namespace where the application resources should be applied.

Answer

It defines the sync frequency.

Answer

It defines the user who triggered the sync.

Answer

It defines the Git repository URL.

Question 7

You are using Kustomize 'overlays' for environment promotion. If you need to add a specific label to all resources in production but not in staging, where should you define it?

Accepted Answer

In the 'overlays/production' kustomization.yaml file.. Kustomize overlays are designed to layer changes on top of a base. The production overlay allows for patching or adding specific labels that don't exist in the base.

Answer

In the global GitOps config map.

Answer

By modifying the manifest manually after deployment.

Answer

In the 'base' directory kustomization.yaml file.

Question 8

What is the impact of enabling 'selfHeal' in an Argo CD Application sync policy?

Accepted Answer

It automatically reverts manual changes to the cluster.. If 'selfHeal' is true, Argo CD will automatically overwrite any manual changes made to the cluster, reverting it to the Git-defined state.

Answer

It automatically creates backups of the cluster state.

Answer

It automatically patches the application with the latest security updates.

Answer

It disables the UI for that application.

Question 9

In the context of GitOps, what is 'Configuration Drift'?

Accepted Answer

The difference between the cluster state and the Git repository state.. Drift occurs when the actual state of the infrastructure or application in the cluster deviates from the intended state defined in Git.

Answer

A security vulnerability in the container image.

Answer

The movement of traffic between blue and green environments.

Answer

The time taken for a Git commit to reach the production cluster.

Question 10

During a blue-green deployment, what is the primary role of the traffic manager (e.g., Istio or Nginx Ingress)?

Accepted Answer

To split traffic between versions to reduce risk.. In blue-green deployments, the traffic manager performs the switch to route users from the old (blue) version to the new (green) version once validation is complete.

Answer

To build the container image.

Answer

To monitor the Git repository for changes.

Answer

To store application logs.

Question 11

You are designing a multi-cluster deployment with Argo CD. You want to avoid defining 50 individual Application manifests. Which feature should you use?

Accepted Answer

Argo CD ApplicationSets.. ApplicationSets use generators (like the Cluster generator) to dynamically create Applications based on cluster list, significantly reducing configuration overhead.

Answer

Helm subcharts.

Answer

Git submodules.

Answer

Kubernetes Custom Resource Definitions (CRDs).

Question 12

What does the 'prune' policy in GitOps do?

Accepted Answer

It deletes resources from the cluster that are no longer in Git.. Pruning removes resources from the cluster that are no longer defined in the source Git repository, ensuring the cluster only contains what is declared.

Answer

It cleans up old container logs.

Answer

It synchronizes the Git repo with the latest upstream changes.

Answer

It restarts pods that have been running for too long.

Question 13

You want to use Helm for your GitOps deployments. Where should the 'values.yaml' file reside for environment-specific overrides?

Accepted Answer

In the Git repository, per environment.. Environment-specific values files (e.g., values-prod.yaml) are typically stored in the Git repository alongside the chart or in a separate environment-specific folder, allowing for clear separation of concerns.

Answer

In a local machine folder not tracked by Git.

Answer

In the Argo CD global settings.

Answer

Inside the container image.

Question 14

In a GitOps promotion pipeline, why is it recommended to tag container images with a unique Git commit SHA instead of 'latest'?

Accepted Answer

To ensure immutability and auditability.. Using the Git commit SHA provides traceability and immutability. 'Latest' is a mutable tag that can point to different versions over time, making rollbacks impossible.

Answer

Because the container registry requires unique SHAs.

Answer

To reduce the size of the container image.

Answer

Because 'latest' is deprecated by Docker.

Question 15

When using Argo CD, how do you handle applications that require resources to be created in a specific order (e.g., CRDs before Operators)?

Accepted Answer

Use syncWaves annotations.. Argo CD 'syncWaves' allow you to assign a numerical value to resources, ensuring they are applied in the correct sequence.

Answer

Use multiple Git repositories.

Answer

Disable automated sync and run it twice.

Answer

Use a single massive YAML file.