ArgoCD Engineer Interview Questions with Answers (2027)
31 Argo CD engineer interview questions on daily operations: sync policy defaults, rollback, projects, RBAC policy.csv, sync waves, hooks, ApplicationSets.
ArgoCD engineer interview questions check whether you can run Argo CD for other teams every day: set up projects and RBAC, write Application specs with the right sync policy, order resources with sync waves and hooks, generate many applications with ApplicationSets, and use the argocd CLI to diff, sync, wait and roll back. This page is about the operator's job, not GitOps theory.
Engineers who own an Argo CD installation get different questions from developers who only use it. Interviewers want to hear that you know the defaults, the guard rails and the commands. If you want GitOps concepts first, read our GitOps with ArgoCD interview questions; for incident-style questions go to the scenario-based ArgoCD questions. Behaviour and syntax below were checked against the Argo CD stable documentation in November 2026, when the latest release on GitHub was v3.6.1.
Key takeaways
- Automated sync does not prune or self-heal unless you set
prune: trueandselfHeal: true. Both are off by default as a safety measure. - You cannot run
argocd app rollbackon an application that has automated sync enabled. - Projects restrict source repositories, destinations and resource kinds. Applications without a project land in the project named
default. - RBAC lives in the
argocd-rbac-cmConfigMap aspolicy.csvandpolicy.default, with built-in rolesrole:readonlyandrole:admin. - Resources sync by phase, then wave (lowest first, default 0), then kind, then name.
- ApplicationSets ship with ten generators, including List, Cluster, Git, Matrix, Merge, Pull Request and OCI.
What the engineer role owns
| Area | What you configure | Where it lives |
|---|---|---|
| Tenancy | AppProjects with repos, destinations and allowed kinds | AppProject resources in Git |
| Access | SSO groups mapped to roles | argocd-rbac-cm |
| Delivery | Application specs and sync policy | Application or ApplicationSet resources |
| Ordering | Sync waves and hooks | Annotations on manifests |
| Day-2 work | Diff, sync, wait, history, rollback | argocd CLI or UI |
Applications and sync policy (questions 1 to 7)
1. What does automated sync with prune and self-heal look like?
spec:
syncPolicy:
automated:
prune: true
selfHeal: true
Automated sync applies changes from Git. prune lets it delete resources that were removed from Git. selfHeal makes it revert manual changes in the cluster.
2. What are the defaults for prune and self-heal?
Both are off. By default automated sync does not delete resources that disappeared from Git, and changes made directly in the cluster do not trigger a sync. Interviewers ask this to see whether you know why a deleted manifest left a resource running.
3. Why can't you roll back an auto-synced application?
The documentation states rollback cannot be performed against an application with automated sync enabled, because the next sync would restore whatever Git says. Disable auto-sync first, roll back, then fix Git and re-enable it. In most teams the better answer is to revert the commit in Git.
4. What is the difference between Synced and Healthy?
Synced means the live state matches Git. Healthy means the resources are working, for example a Deployment has its replicas available. An app can be Synced and Degraded if the manifest is applied but pods crash.
5. How do you see what a sync will change before running it?
Use argocd app diff to compare target and live state, or open the diff view in the UI. Review it in change windows before a manual sync.
6. How do you make a pipeline wait for a deploy?
Run argocd app wait, which waits for the application to be synced and healthy. Use it as a pipeline step after the Git commit so the pipeline fails if the rollout fails.
7. Which argocd app commands do you use most?
argocd app list
argocd app get my-app
argocd app diff my-app
argocd app sync my-app
argocd app wait my-app
argocd app history my-app
argocd app rollback my-app <history-id>
argocd app terminate-op my-app
terminate-op stops a running operation, which you need when a sync hangs on a hook.
Projects and RBAC (questions 8 to 14)
8. What does an AppProject restrict?
Which Git repositories applications can deploy from (sourceRepos), which clusters and namespaces they can deploy to (destinations), which cluster-scoped kinds are allowed (clusterResourceWhitelist) and which namespaced kinds are blocked (namespaceResourceBlacklist). Project roles grant access through policies bound to OIDC groups or JWT tokens.
9. Why should teams avoid the default project?
Applications with no project go into default, which is usually wide open. Give each team its own project limited to its repos and namespaces so one team cannot deploy into another team's namespace or create cluster-wide resources.
10. Where is RBAC configured?
In the argocd-rbac-cm ConfigMap in the argocd namespace, under the policy.csv and policy.default keys.
11. Write a policy that lets a group sync apps in one project.
p, role:team-a-deployer, applications, get, team-a/*, allow
p, role:team-a-deployer, applications, sync, team-a/*, allow
g, team-a-devs, role:team-a-deployer
The policy format is p, subject, resource, action, object, effect, and for applications the object is project/app. The g line maps an SSO group to the role.
12. What do the built-in roles allow?
role:readonly gives read access to all resources. role:admin gives unrestricted access.
13. Why is a broad policy.default risky?
Every authenticated user gets the default role, and the documentation warns that default permissions cannot be blocked by a deny rule. Use a minimal custom role as the default and grant more through group mappings.
14. How do you test an RBAC change?
Apply it in a non-production instance first and check it with the CLI's RBAC validation and can-i commands for your version, then log in as a test user from the target group. Keep the ConfigMap in Git so a bad change is one revert away.
Ordering, hooks and ApplicationSets (questions 15 to 21)
15. How do sync waves work?
Add the argocd.argoproj.io/sync-wave annotation with a number. Resources default to wave 0, lower waves sync first and negative values are allowed. Argo CD sorts by phase, then wave, then kind (namespaces first, then other Kubernetes resources, then custom resources), then name.
16. Which hook phases exist?
PreSync, Sync, Skip, PostSync, SyncFail, PreDelete and PostDelete. PostDelete has been available since v2.10. Set the phase with the argocd.argoproj.io/hook annotation.
17. Show a database migration hook.
apiVersion: batch/v1
kind: Job
metadata:
name: db-migrate
annotations:
argocd.argoproj.io/hook: PreSync
argocd.argoproj.io/hook-delete-policy: HookSucceeded
spec:
template:
spec:
restartPolicy: Never
containers:
- name: migrate
image: registry.example.com/app-migrate:1.4.2
args: ["migrate", "up"]
The Job runs before the main sync and is deleted when it succeeds.
18. What hook delete policies exist and what is the default?
HookSucceeded, HookFailed and BeforeHookCreation. If you set none, Argo CD uses BeforeHookCreation, which deletes the old hook resource before creating a new one.
19. When would you use an ApplicationSet?
When you would otherwise copy the same Application many times, such as one app per cluster, per environment or per directory in a monorepo. The ApplicationSet controller generates the Applications from a template and parameters.
20. Which generators are available?
List, Cluster, Git, Matrix, Merge, SCM Provider, Pull Request, Cluster Decision Resource, Plugin and OCI. Matrix and Merge combine other generators, for example every cluster crossed with every app directory.
21. How would you create preview environments for pull requests?
Use the Pull Request generator so each open pull request gets its own Application, with the branch and number templated into the namespace. When the pull request closes, the generated Application is removed. Give these apps their own project with tight destination limits.
Scenario questions (questions 22 to 30)
22. A resource deleted from Git is still running.
Prune is off. Either enable prune: true in the sync policy or run a manual sync with prune. Check the diff first so you do not delete something another team expects.
23. Someone scaled a Deployment by hand and Argo CD did not revert it.
Self-heal is off, so manual changes do not trigger a sync. Enable selfHeal if the team wants Git to win, or ignore the replica field if an autoscaler manages it.
24. Rollback from the UI is greyed out during an incident.
The application has automated sync enabled. Disable auto-sync, roll back to the last good history entry, then revert the bad commit in Git and turn auto-sync back on.
25. A sync is stuck on a PreSync hook.
Check the hook Job's pods and logs. If the migration hangs, run argocd app terminate-op to stop the operation, fix the cause and sync again.
26. CRDs and the custom resources that use them fail on first sync.
The custom resources were applied before their CRD existed. Put CRDs in an earlier wave, or in a separate application that syncs first.
27. A team deployed a ClusterRole they should not have.
Their project allows cluster-scoped kinds. Tighten clusterResourceWhitelist to the kinds the team needs (often none), and move shared cluster resources to a platform project.
28. A new hire can see every application.
Check policy.default. If it is role:readonly, every authenticated user reads every app. Replace it with a minimal role and grant project access through SSO groups.
29. An ApplicationSet change deleted apps in several clusters.
The generator output changed and the controller removed Applications that no longer matched. Review generator changes like code, test them against a non-production instance and look at the ApplicationSet's sync policy options that control deletion before rolling out.
30. How do you upgrade Argo CD with confidence?
Read the upgrade notes for every version you cross, upgrade a staging instance first, watch for deprecated fields in Application and ApplicationSet specs, and keep the install manifests or Helm values in Git so rollback is a revert.
31. A team asks for a second Argo CD instance of its own. What do you say?
Ask what problem they are solving first. Separate projects with their own repos, destinations and RBAC groups usually give enough isolation on one instance and keep upgrades in one place. A separate instance makes sense when the team needs different SSO, a different upgrade schedule or a hard security boundary between environments. Write the decision down so the next team gets the same answer.
How to prepare
Run Argo CD in a local cluster, create two projects for two fake teams, wire RBAC to two groups, and deploy one app with a PreSync migration hook and one ApplicationSet across two namespaces. Then try every scenario above on purpose. Being able to say "I hit this, and here is the command I used" is what this round rewards.
More practice: real-time ArgoCD questions, advanced ArgoCD questions for architect rounds and the most asked ArgoCD questions for a quick review. To compare Argo CD with other options, see 8 GitOps tools for Kubernetes automation.
Argo CD sits on top of Kubernetes skills. Our CKA training runs in the classroom in Kharadi, Pune and live online across India.
Frequently asked questions
Does Argo CD prune resources by default?
No. Automated sync does not delete resources removed from Git unless you set prune to true.
Why can't I roll back my Argo CD application?
Rollback is not allowed on an application with automated sync enabled. Disable auto-sync first or revert the commit in Git.
Where is Argo CD RBAC configured?
In the argocd-rbac-cm ConfigMap, using the policy.csv and policy.default keys.
What is the default sync wave?
Wave 0. Lower waves sync first and negative values are allowed.
What is the default hook delete policy?
BeforeHookCreation, if no delete policy is set.
How many ApplicationSet generators are there?
The documentation lists ten: List, Cluster, Git, Matrix, Merge, SCM Provider, Pull Request, Cluster Decision Resource, Plugin and OCI.
What is the latest Argo CD version?
The latest release on the Argo CD GitHub releases page was v3.6.1 when this guide was checked in November 2026. Check the releases page before an interview.
Official references
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0