drift
DevOps interview questions tagged drift, across every topic.
6 questions · 2 unlocked for you
Concepts behind "drift"
The concept pages behind what these questions are testing.
Foundational
Immutable infrastructure, and the replacement nobody planned forImmutability means a change produces a new resource rather than an edited one, which supports reproducibility when definitions and inputs are controlled. It also means some innocuous-looking edits destroy and recreate a live resource, and knowing which ones is the difference between a routine plan and an outage.🏗️ Declarative Infrastructure
Foundational
Model quality degrades without touching a single infrastructure metricClassical dependencies and models can both return incorrect results without an error. A model fails by returning something plausible and wrong, which every status-code-based metric records as a success. Quality needs its own signals, its own threshold and its own budget, or it is unobservable until a customer complains.🤖 AI Infrastructure
Core
State and drift: why infrastructure as code needs a ledgerTerraform state is not a cache and not an optimisation. It is the mapping between the names in your configuration and the identifiers in the provider, and without it there is no way to know whether a resource in your code is the same resource that exists in the cloud. Every confusing Terraform behaviour, from destroy and recreate to import, follows from what state is for.🏗️ Declarative InfrastructureSign in
Core
GitOps: reconciliation, not deploymentGitOps is the Kubernetes control loop applied to your deployments: a controller compares live resources to versioned desired state and reconciles configured differences. The distinction from a pipeline that runs kubectl apply is not tooling preference. It changes what happens when someone edits the cluster directly, and it changes who holds cluster credentials.🚀 Delivery & GitOpsSign in