Explain Terraform lifecycle meta-arguments.
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Terraform & IaC conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
The lifecycle block controls how Terraform creates, updates, and destroys a resource.
- create_before_destroy: create the replacement before destroying the old one, reducing downtime for resources that must be replaced.
- prevent_destroy: fails the plan if the resource would be destroyed. Useful for databases and state buckets.
- ignore_changes: ignores changes to listed attributes, useful when an external system or autoscaler modifies them.
- replace_triggered_by: forces replacement when a referenced resource or attribute changes.
- precondition and postcondition: validate assumptions before or after an operation.
resource "aws_db_instance" "db" {
lifecycle {
prevent_destroy = true
ignore_changes = [tags["LastModified"]]
}
}
Caveats: prevent_destroy does not protect against state removal or CLI deletes. ignore_changes can hide real drift. create_before_destroy requires no name conflicts. Use these deliberately and document why.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.