You are implementing progressive delivery using Flagger. After a Canary resource is defined, which metric is most critical for Flagger to automatically rollback a deployment during a blue/green shift?
You are managing environment promotion by overlaying Kustomize patches for 'prod', 'staging', and 'dev'. Which TWO of the following practices follow the GitOps principle of 'single source of truth' for environment configuration?
Your organization uses the App-of-Apps pattern in Argo CD to manage hundreds of microservices. You need to ensure that when a developer updates a repository structure, the root application automatically discovers and syncs new child applications without manual intervention. Which feature should be enabled in the Application resource?
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?
In a multi-cluster GitOps setup using Argo CD, you need to ensure that specific secrets are only synced to a production cluster. Which approach is the most secure?
You are using the App-of-Apps pattern in Argo CD to manage hundreds of microservices. You notice that the parent application is stuck in a 'Syncing' state indefinitely. What is the most likely cause?
You are implementing the App-of-Apps pattern using Argo CD. You have a root Application that points to a Helm chart containing multiple sub-Application manifests. When you update the source Git repository, some sub-applications remain in an 'OutOfSync' state while others update successfully. What is the most likely cause?
When using the 'Git-generator' in ApplicationSet, you want to include only a subset of directories based on a specific file content. Which feature of ApplicationSet allows you to filter the directories discovered?
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)
You are adopting GitOps for a team that will deploy the same Helm chart to many ephemeral preview environments. Each environment needs a unique hostname and a different replica count, and you want to avoid maintaining a separate values file for every environment. Which GitOps pattern should you implement?
You are designing a GitOps workflow for a team that wants to use a pull-based model with Argo CD. The team requires that all changes to production be reviewed and approved before deployment, and that the deployment automatically rolls back if the application becomes unhealthy. Which two patterns should you implement? (Choose two.)
In a multi-cluster GitOps architecture using Argo CD, how do you manage credentials for a remote cluster that is not the cluster where Argo CD resides?
In a blue-green progressive delivery deployment using Flagger, you notice that the 'primary' service is not receiving traffic even after the analysis successfully completes. What is the most likely cause?
You are deploying applications across multiple clusters using Argo CD. You want to implement a hub-and-spoke model where the central management cluster controls all edge clusters. Which THREE of the following are necessary to correctly configure this pattern?
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?
You are managing a large-scale deployment using the App-of-Apps pattern in Argo CD. Which resource type do you primarily use as the parent application to reference child application manifests?
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?
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?
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?
You are designing a multi-cluster deployment with Argo CD. You want to avoid defining 50 individual Application manifests. Which feature should you use?
You are using Argo Rollouts for progressive delivery. You want to execute a 'AnalysisRun' before switching traffic. Where is the 'AnalysisTemplate' defined?
If you have a multi-cluster setup and you want to ensure that 'production' clusters only pull images from a hardened internal registry, how can you enforce this in GitOps?
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?
When deploying across multiple clusters using Argo CD, you need to ensure that specific secrets are only available to clusters located in the 'us-east' region. Which resource should you use to enforce this segregation?
You are performing a Canary deployment using Argo Rollouts. You notice that the analysis template is failing even though the metrics are within range. What is the most common cause of this in a GitOps workflow?
In a multi-cluster GitOps environment, you are using the ApplicationSet controller with a 'Cluster Generator'. You need to add a new cluster dynamically without modifying the ApplicationSet manifest. How should you achieve this?
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?
You are implementing a GitOps promotion workflow where each environment (dev, staging, prod) has its own Kubernetes namespace in a single cluster. Your team wants to keep the base manifests identical and only vary replicas, resource limits, and image tags per environment. Which pattern should you use to achieve this with minimal duplication?
You are using Argo CD to manage a production application. A developer accidentally commits a change that sets the replica count to zero, and the change is merged to the main branch. You want to prevent this from happening again without blocking all changes to the repository. Which GitOps pattern should you implement?
You are managing a GitOps repository that contains both application manifests and cluster-wide configurations. You want to ensure that changes to cluster-wide configurations are applied before application workloads during a sync. Which Argo CD feature should you use?
You are using Flux CD to manage a multi-tenant cluster. Each tenant has its own Git repository and namespace. You want to ensure that a tenant's Kustomization can only deploy resources into its own namespace and cannot modify cluster-scoped resources. Which Flux feature should you configure?