← 🏗️ Declarative Infrastructure
Advanced
Terraform state locking: concurrent writers, stale plans and recovery
Reason about concurrent Terraform runs, backend locking and saved-plan freshness. Diagnose an orphaned lock and distinguish safe recovery from creating two active writers.
View Premium accesscourse lessons, concepts and answers · see current terms
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Infrastructure as Code & ConfigurationTwo engineers run terraform apply against the same backend at the same time. What happens?→Infrastructure as Code & ConfigurationName three things in the Terraform state file, and explain why it is a security artifact rather than a cache.→Infrastructure as Code & ConfigurationPick and defend a remote state backend for a 40-engineer platform. Compare the realistic options.→Infrastructure as Code & ConfigurationWalk me through terraform init, plan, apply and destroy. What is each one actually doing?→Infrastructure as Code & Configurationcount versus for_each in Terraform: when does list ordering cause a destroy and recreate?→Infrastructure as Code & ConfigurationOne Terraform module tree, three environments. How do you lay out state so a production apply can never touch anything else?→