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.

Practice

1. What is the main purpose of using ArgoCD in a Kubernetes environment with GitOps?

easy

A. To replace Kubernetes with a new container orchestration system

B. To manually deploy applications without using Git

C. To store container images in a private registry

D. To automatically sync Kubernetes cluster state with Git repository configurations

Solution

1. Step 1: Understand GitOps concept

   GitOps uses Git as the single source of truth for application configurations.

2. Step 2: Role of ArgoCD in GitOps

   ArgoCD automatically syncs Kubernetes cluster state to match the Git repo, ensuring deployments are consistent and automated.

3. Final Answer:

   To automatically sync Kubernetes cluster state with Git repository configurations -> Option D

4. Quick Check:

   GitOps = Auto-sync cluster with Git [OK]

Hint: Remember: ArgoCD syncs cluster state from Git automatically [OK]

Common Mistakes:

• Thinking ArgoCD replaces Kubernetes
• Believing ArgoCD deploys apps manually
• Confusing ArgoCD with container registries

2. Which of the following is the correct ArgoCD CLI command to create an application named myapp syncing from Git repo https://github.com/example/repo.git with path k8s and target cluster https://kubernetes.default.svc?

easy

A. argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default

B. argocd create app myapp --repository https://github.com/example/repo.git --directory k8s --cluster https://kubernetes.default.svc

C. kubectl create app myapp --repo https://github.com/example/repo.git --path k8s

D. argocd app new myapp --repo-url https://github.com/example/repo.git --folder k8s --server https://kubernetes.default.svc

Solution

1. Step 1: Identify correct ArgoCD CLI syntax

   The correct command uses argocd app create with flags --repo, --path, --dest-server, and --dest-namespace.

2. Step 2: Compare options

   argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default matches the official syntax exactly. Others use incorrect commands or flags.

3. Final Answer:

   argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default -> Option A

4. Quick Check:

   Correct CLI syntax = argocd app create myapp --repo https://github.com/example/repo.git --path k8s --dest-server https://kubernetes.default.svc --dest-namespace default [OK]

Hint: Remember: 'argocd app create' plus repo, path, dest-server flags [OK]

Common Mistakes:

• Using kubectl instead of argocd CLI
• Wrong flag names like --repository or --folder
• Incorrect command order or missing --dest-namespace

3. Given the following ArgoCD Application YAML snippet, what will happen when ArgoCD syncs this app?

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: sample-app
spec:
  source:
    repoURL: https://github.com/example/app-configs.git
    path: production
  destination:
    server: https://kubernetes.default.svc
    namespace: default
  syncPolicy:
    automated: {}

medium

A. ArgoCD will reject the app because syncPolicy is empty

B. ArgoCD will only show the app status but not deploy it automatically

C. ArgoCD will automatically deploy and keep the app in sync with the Git repo

D. ArgoCD will deploy the app once but not update it on Git changes

Solution

1. Step 1: Understand syncPolicy automated

   The syncPolicy: automated: {} means ArgoCD will auto-sync changes from Git to cluster.

2. Step 2: Effect on deployment

   ArgoCD will deploy the app initially and keep it updated automatically when Git changes.

3. Final Answer:

   ArgoCD will automatically deploy and keep the app in sync with the Git repo -> Option C

4. Quick Check:

   syncPolicy automated = auto deploy and sync [OK]

Hint: syncPolicy automated means auto deploy and keep in sync [OK]

Common Mistakes:

• Thinking empty braces mean no automation
• Assuming manual sync is required
• Confusing syncPolicy with app rejection

4. You created an ArgoCD app but it shows OutOfSync status even after you committed changes to Git. Which of the following is the most likely cause?

medium

A. The app's syncPolicy is not set to automated, so manual sync is needed

B. The Git repository URL is incorrect and unreachable

C. The Kubernetes cluster is down and cannot apply changes

D. The app name in ArgoCD does not match the Git repo name

Solution

1. Step 1: Understand OutOfSync status

   OutOfSync means cluster state differs from Git repo state.

2. Step 2: Check syncPolicy effect

   If syncPolicy is not automated, ArgoCD won't auto-apply changes; manual sync is required.

3. Final Answer:

   The app's syncPolicy is not set to automated, so manual sync is needed -> Option A

4. Quick Check:

   OutOfSync + no automated sync = manual sync needed [OK]

Hint: OutOfSync often means no automated sync set [OK]

Common Mistakes:

• Assuming cluster is down without checking
• Blaming Git URL without error evidence
• Thinking app name mismatch causes OutOfSync

5. You want to ensure that ArgoCD only deploys changes to your Kubernetes cluster after manual approval, but still track changes in Git automatically. Which configuration should you use in your ArgoCD Application YAML?

hard

A. Set syncPolicy: automated: {} to enable auto deploy

B. Omit syncPolicy and use manual sync to approve changes

C. Set syncPolicy: automated: null to disable auto deploy

D. Set syncPolicy: automated: { prune: true, selfHeal: true } for auto deploy with cleanup

Solution

1. Step 1: Understand manual approval need

   To require manual approval before deployment, auto sync must be disabled.

2. Step 2: Configure syncPolicy accordingly

   Omitting syncPolicy disables auto sync, so ArgoCD tracks Git but waits for manual sync.

3. Final Answer:

   Omit syncPolicy and use manual sync to approve changes -> Option B

4. Quick Check:

   No syncPolicy = manual approval required [OK]

Hint: No syncPolicy means manual sync only [OK]

Common Mistakes:

• Using automated sync disables manual approval
• Setting automated with prune/selfHeal still auto deploys
• Setting automated: null is invalid syntax