GitOps with ArgoCD in Kubernetes - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary role of ArgoCD in a GitOps workflow?

Choose the best description of what ArgoCD does in a GitOps setup.

A It provides a graphical interface for writing Kubernetes manifests manually.

B It builds Docker images from source code and pushes them to container registries.

C It manages user authentication and authorization for Kubernetes clusters.

D It continuously monitors a Git repository and syncs Kubernetes clusters to match the declared state.

💡 Hint

Think about how GitOps keeps Kubernetes clusters in sync with Git.

ArgoCD watches Git repositories for changes and applies those changes to Kubernetes clusters automatically, ensuring the cluster state matches the Git state.

💻 Command Output

intermediate

What is the output of this ArgoCD CLI command?

Given the command argocd app list, what output will you see if no applications are currently managed by ArgoCD?

Kubernetes

argocd app list

A

NAME  PROJECT  SYNC STATUS  HEALTH STATUS

B Error: No connection to cluster

C No applications found

D Application list is empty

💡 Hint

Consider the default table headers ArgoCD shows even if no apps exist.

ArgoCD shows the table headers for applications even if none exist, so the output includes the column names but no app rows.

🔀 Workflow

advanced

Identify the correct sequence to deploy an app with ArgoCD using GitOps

Put these steps in the correct order to deploy a Kubernetes app using ArgoCD and GitOps.

A 2,1,3,4

B 1,2,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about how GitOps starts from Git and then ArgoCD syncs.

First, manifests are created and committed to Git. Then ArgoCD is configured to watch that repo. ArgoCD syncs changes to the cluster, and finally you verify the app.

❓ Troubleshoot

advanced

What error will occur if ArgoCD cannot access the Git repository due to wrong credentials?

When ArgoCD tries to sync an application but the Git repository credentials are incorrect, what error message will you most likely see?

A Error: Kubernetes API server not reachable

B Sync successful: no changes detected

C Failed to sync: repository unreachable: authentication failed

D Application health status: Healthy

💡 Hint

Think about what happens when authentication to Git fails.

ArgoCD reports a failure to sync because it cannot authenticate to the Git repository, showing an authentication failed message.

✅ Best Practice

expert

Which practice ensures safe automated syncs in ArgoCD for production environments?

Choose the best practice to avoid accidental overwrites or downtime when ArgoCD automatically syncs changes to a production Kubernetes cluster.

A Use automated sync only for development clusters and manual sync for production.

B Disable automated sync and perform all syncs manually to avoid any risk.

C Enable automated sync with <code>prune</code> and <code>selfHeal</code> without any manual intervention.

D Enable automated sync with <code>prune</code> and <code>selfHeal</code> but require manual approval for syncs.

💡 Hint

Consider balancing automation benefits and safety in production.

Using automated sync in development speeds up testing, but manual sync in production reduces risk of accidental downtime or data loss.