Interview › Infrastructure as Code (Terraform, Ansible)
What is a Terraform registry module, and how do you evaluate one for production use?
Infrastructure as Code (Terraform, Ansible) · Intermediate level
Answer
A Terraform registry module is a published reusable module from the public or private registry. For production, I evaluate maintainership, source code quality, versioning, examples, inputs/outputs, security defaults, issue history, release cadence, license, and whether it allows the controls my organization requires.
Technical explanation
A good module has narrow scope and predictable behavior.
Avoid unmaintained modules, modules with excessive permissions, or modules that hide security decisions.
Pin module versions and read changelogs before upgrades.
Keep Terraform's ownership boundary clear: one state should own a resource or field, and other tools should consume published outputs instead of modifying it.
Use fmt, validate, linting, policy checks, plan review, and state locking before production applies.
Design for small blast radius by splitting state around lifecycle, permissions, and recovery boundaries.
Hands-on example
1. Build a safe IaC delivery workflow for: What is a Terraform registry module, and how do you evaluate one for production use?
2. Pull request job:
terraform fmt -check
terraform init -backend=false
terraform validate
tflint --recursive
checkov -d .
terraform init
terraform plan -out=tfplan
terraform show -json tfplan > tfplan.json
3. Policy job evaluates plan JSON for public exposure, missing encryption, IAM wildcards, and destructive changes.
4. Apply job runs only after approval, uses remote state locking, short-lived cloud credentials, and applies the saved plan artifact.
5. For failures, rerun plan, inspect state and cloud objects, and fix root cause before any state surgery.
Check how well your resume matches the role with our free resume checker— match score, ATS check, and the skills you're missing.
More Infrastructure as Code (Terraform, Ansible) interview questions
- What is Infrastructure as Code, and what problems does it solve over click-ops?
- What is the difference between declarative and imperative IaC, and where do Terraform and Ansible fall?
- What is the difference between configuration management and provisioning?
- What is Terraform, and what is the core plan/apply workflow?
- What does terraform init do?
- What is the Terraform state file, and why is it critical?
- Why should state be stored remotely, and what backend would you use on AWS?
- What is state locking, and why does it matter for teams?