CGOA Practice Test 1 — 30 Questions

Question 1

You want to promote a microservice from staging to production using the 'Git Branch' strategy. Which configuration allows you to ensure the exact same container image SHA is used across both environments?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Use a common Helm chart with environment-specific values files.. Using image tags like 'latest' is non-deterministic. Referencing the specific SHA in the Git manifest for the production branch ensures consistency.

Answer

Manually update the container image using kubectl edit.

Answer

Use a different container registry for production.

Answer

Change the image tag to 'production' in the deployment manifest.

Question 2

Which THREE of the following are benefits of the 'App-of-Apps' pattern? (Select three)

Accepted Answer

It enables hierarchical synchronization of applications.. App-of-Apps simplifies large scale management, allows for grouping of related services, and enables hierarchical control of GitOps deployments.

Answer

It ensures all applications use the exact same image tag.

Answer

It eliminates the need for container registries.

Question 3

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 4

You are implementing progressive delivery with Flagger. You notice that the canary analysis is failing despite the new version being stable. What is the most common reason for this?

Accepted Answer

The Prometheus query for success rate is returning no data.. Flagger requires specific metrics (like HTTP request success rate) to be present to validate a canary. If the metrics provider (e.g., Prometheus) is not configured, the analysis cannot proceed.

Answer

The deployment strategy is set to 'Immediate' instead of 'Canary'.

Answer

The Git repository is in read-only mode.

Answer

The service mesh sidecar is missing the 'canary' annotation.

Question 5

Which TWO of the following are valid strategies for promoting an application from staging to production in GitOps? (Select two)

Accepted Answer

Merging a pull request from a staging branch to a production branch.. Promotion strategies include changing the Git reference (branch/tag) or updating the values file within a single repository path.

Answer

Deleting the application and recreating it.

Answer

Running a 'kubectl rollout undo' command manually.

Answer

Bypassing the CI/CD pipeline by pushing directly to the cluster.

Question 6

Your organization uses a 'Git-branch-per-environment' strategy. You notice that hotfixes applied to the 'production' branch are being overwritten by automatic merges from the 'staging' branch. Which GitOps promotion pattern should you adopt to prevent this drift?

Accepted Answer

Switch to a repository structure using Kustomize overlays with a single branch.. The 'Pull Request based promotion' pattern ensures that changes are explicitly reviewed and merged from staging to production, rather than relying on automated long-running branch merges that cause conflicts.

Answer

Enable Argo CD 'automated.allowEmpty' sync options.

Answer

Implement an automated CI job to force push the staging branch to production.

Answer

Use Argo CD ApplicationSets with a 'git' generator to deploy only from the main branch.

Question 7

When promoting an application from staging to production using the 'GitOps directory' pattern, what is the most robust way to ensure environment-specific configurations are applied correctly?

Accepted Answer

Using Kustomize overlays for each environment. Using Kustomize overlays allows for a base configuration with environment-specific patches, ensuring no drift between environments.

Answer

Hardcoding environment names inside the main deployment file

Answer

Dynamic shell scripting in the CI pipeline

Answer

multiple_choice

Answer

Copy-pasting YAML files across folders

Question 8

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 9

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 10

You have a GitOps pipeline where you want to promote a change from Staging to Production. Using Argo CD, what is the recommended way to perform this promotion?

Accepted Answer

Update the version in the Git manifest for the Production Application and commit.. Updating the image tag or configuration in the Production folder/branch within the Git repository is the standard GitOps way to trigger a promotion, as it maintains Git as the single source of truth.

Answer

Update the ApplicationSet generator to point to a different branch.

Answer

Run 'argocd app sync' pointing to the staging image.

Answer

Use the 'kubectl patch' command on the production deployment.

Question 11

What is the primary benefit of using a 'Git Branch' promotion pattern over a 'Directory-based' promotion pattern?

Accepted Answer

It allows teams to use PRs to review configuration changes for specific environments.. Branch-based promotion allows for better isolation of changes, enabling PR reviews for individual environments and preventing accidental merges to production.

Answer

It eliminates the need for CI pipelines.

Answer

It requires less storage space in the Git repository.

Answer

It automatically synchronizes all branches to the cluster simultaneously.

Question 12

Why should you avoid using 'latest' as a container image tag in GitOps?

Accepted Answer

It prevents the controller from knowing exactly what version is deployed.. Using 'latest' makes the deployment non-deterministic because the image associated with the tag can change, making it impossible to know exactly what is running in the cluster.

Answer

It causes the cluster to crash.

Answer

It's slower to pull.

Answer

It requires more storage space.

Question 13

Which TWO of the following are common reasons for a deployment to be marked as 'Degraded' by Argo CD? (Select two)

Accepted Answer

The health checks defined for the application are failing.. 'Degraded' status often occurs when pods fail to start (e.g., CrashLoopBackOff) or when health checks defined in the manifest are not met.

Answer

The user manually changed a label.

Answer

The Argo CD controller is overloaded.

Answer

The Git repository is temporarily offline.

Question 14

What is the recommended way to handle secrets in GitOps?

Accepted Answer

Use an encrypted secret operator like SealedSecrets.. Secrets should never be stored in plaintext. Tools like SealedSecrets or HashiCorp Vault integration are standard.

Answer

Commit them directly to the repo in a private branch.

Answer

Create them manually using kubectl.

Answer

Store them in base64 in Git.

Question 15

Which TWO benefits does GitOps provide for team collaboration?

Accepted Answer

Providing a transparent, versioned history of infrastructure changes.. GitOps fosters collaboration by leveraging pull requests for peer reviews and providing a single, transparent record of all changes.

Answer

Removing the need for communication.

Answer

Forcing everyone to use the same IDE.

Answer

Allowing developers to deploy without oversight.

Question 16

Which THREE activities are part of the 'Automated Pull-Based Reconciliation' process?

Accepted Answer

Applying updates to the cluster API.. The process involves detecting changes, fetching manifests, and applying them.

Answer

Sending a push notification to developers.

Answer

Compiling binaries on the local cluster node.

Question 17

In GitOps, what is the 'Source of Truth'?

Accepted Answer

The Git repository.. The Git repository is the single source of truth for the desired state of the infrastructure and applications.

Answer

The running Kubernetes cluster.

Answer

The CI pipeline logs.

Answer

The container registry.

Question 18

Which TWO of the following configurations are necessary to ensure that GitOps-managed clusters in a multi-cluster setup remain isolated from one another? (Select TWO)

Accepted Answer

Implementing unique namespaces for each application.. Using dedicated AppProjects per cluster and strict namespace-level RBAC ensures that GitOps controllers cannot accidentally deploy or interfere with resources in unauthorized clusters.

Answer

Disabling the GitOps controller on the management cluster.

Answer

Using the same Git repository for all clusters.

Answer

Enabling 'automated.prune' on all applications.

Question 19

When managing multiple environments (dev/stage/prod) in one repository, which folder structure is generally considered best practice?

Accepted Answer

Using environment-specific folders.. Keeping environment configurations in separate folders (e.g., /overlays/dev, /overlays/prod) allows for clear separation and prevents accidental configuration bleeding.

Answer

Storing configurations in the application code folder.

Answer

Putting everything in a single root folder.

Answer

Using different Git repos for every single manifest.

Question 20

Which THREE of the following are common challenges when scaling GitOps to hundreds of clusters? (Select three)

Accepted Answer

Automatic rollbacks when the Git repo is empty.. Scaling challenges include managing the overhead of the controller, handling secret distribution, and ensuring that temporary outages do not lead to massive drift across the fleet.

Answer

The need for a dedicated team just to write Dockerfiles.

Answer

Increased dependency on internet speed.