Your organization is transitioning from imperative scripts to Infrastructure as Code (IaC) using Terraform. You need to ensure that the infrastructure state remains synchronized with the Git repository after every commit. Which approach best aligns with GitOps principles?
Your organization wants to implement DevSecOps by integrating security scanning into a GitOps pipeline. Where should the vulnerability scan happen to prevent insecure configurations from ever reaching the cluster?
A company uses Terraform for IaC and Argo CD for application delivery. How should they manage the dependency between infrastructure provisioning and app deployment to ensure GitOps consistency?
You are debugging a drift in a GitOps environment. The cluster state differs from the Git repository. What is the most likely cause if you are using Flux?
A team is transitioning from traditional imperative scripts to declarative Configuration as Code. Which approach best satisfies the GitOps principle of using a desired state definition?
What is the most effective approach to handle 'secrets' in GitOps when you require strict compliance that mandates secrets never exist in plain text in the repo?
You are managing a global cluster setup with GitOps. How do you handle configuration that must be identical across all clusters while allowing for regional variations?
A security auditor asks how your team handles secret management in a GitOps environment without exposing sensitive credentials in the Git repository. What is the standard GitOps practice for this requirement?
Your team is integrating a CI pipeline with a GitOps delivery model. Which of the following tasks should remain in the CI pipeline, and which should be moved to the CD/GitOps reconciliation process?
You are migrating a legacy application deployment process to GitOps. The application requires a specific sequence of database migrations to run before the new container version is deployed. How do you implement this in a GitOps-friendly way?
In the context of 'Configuration as Code', why is it considered a best practice to use a declarative manifest format (like YAML) rather than imperative commands?
Your organization uses a 'GitOps Operator' to manage deployments. What happens if a developer manually changes a configuration on the Kubernetes cluster using 'kubectl edit'?
Your platform team runs a GitOps operator that continuously reconciles a Kubernetes cluster against a Git repository. A compliance auditor asks how you can prove that no unapproved manual changes have been applied to production over the last 90 days. Which practice should you implement to satisfy this requirement?
A platform team runs a GitOps operator that continuously reconciles cluster state from a Git repository. A compliance auditor asks how the team can prove which commit produced the configuration currently running in production six weeks ago, after many merges and rollbacks. Which practice best satisfies this requirement?
A team adopting GitOps wants to reduce the blast radius of a bad change and shorten mean time to recovery. They already store all manifests in Git and use an operator for reconciliation. Which practice most directly limits the impact of a faulty change reaching production?
An organization separates its GitOps repositories into an application repo and an environment configuration repo. Developers merge frequently into the application repo, while the environment repo pins image digests. A release engineer must promote a tested build from staging to production. Which action aligns with this separation of concerns?
A team is designing a GitOps workflow and wants to enforce policy and compliance before changes reach production clusters. Which two practices fit a GitOps-aligned governance model? (Choose two.)
A team wants to detect when someone manually edits a live resource so that the cluster diverges from Git. Their operator reconciles every five minutes. What is the most accurate statement about detection and remediation in this setup?