HashiCorp calls provisioners a last resort and expects you to say why in concrete terms: tainted resources, invisible drift, SSH reachability. Then name what replaces each legitimate use.
an account raises the per-topic limit · no card
← Infrastructure as Code & Configuration / 12
easyNewHashiCorpTCSInfosys
You spot a local-exec provisioner in a production Terraform module. Make the case for keeping or killing it.
HashiCorp calls provisioners a last resort and expects you to say why in concrete terms: tainted resources, invisible drift, SSH reachability. Then name what replaces each legitimate use.
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 trackPick and defend a remote state backend for a 40-engineer platform. Compare the realistic options.Next in this trackTrace a database password from your Terraform pipeline to the resource. Where can it leak, and what closes each hole?Next in this trackDesign the CI checks for a Terraform repository. What runs at each stage, and what can each check never catch?
DISCUSSION · 0
Nothing here yet. Say how you would answer it.