One ForceNew attribute turns an edit into a destroy. Know the schema mechanics, the four lifecycle levers, and why create_before_destroy trades downtime for name collisions.
an account raises the per-topic limit · no card
← Infrastructure as Code & Configuration / 16
mediumNewHashiCorpFlipkartSwiggy
A routine change wants to replace a production resource. How do Terraform updates become replacements, and what controls that?
One ForceNew attribute turns an edit into a destroy. Know the schema mechanics, the four lifecycle levers, and why create_before_destroy trades downtime for name collisions.
Updated Sep 2026 · Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.
UP NEXT ON YOUR JOURNEY
Next in this trackAn apply planned to destroy and recreate the production database. Which lifecycle arguments belonged on that resource?Next in this trackA module needs an AMI ID and three subnet IDs. Do you hardcode them, accept variables, or look them up?Next in this trackThirty teams ship from one Terraform repository. How do you cut it into stacks so one bad apply cannot touch everyone?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.