Question 1

Why use Terraform in DevOps teams?

Accepted Answer

Terraform allows teams to define infrastructure declaratively in version-controlled files instead of creating resources manually through consoles.

This improves consistency, reviewability, and repeatability across environments. It also supports automation and makes infrastructure changes easier to track and audit.

Question 2

What is Terraform state, and why is it important?

Accepted Answer

Terraform state maps configured resources to real infrastructure objects so Terraform can calculate what needs to be created, updated, or destroyed.

State is important because Terraform is not just reading code; it is comparing desired configuration with known real-world resources. Without reliable state, safe planning and change management become much harder.

Question 3

Why should Terraform state usually be stored remotely?

Accepted Answer

Remote state supports team collaboration, access control, locking, backup, and reduced risk of accidental corruption or loss.

This matters because local state works poorly in shared environments. If multiple people run Terraform independently without coordinated state management, drift and conflicting changes become much more likely.

Question 4

What is the difference between `terraform plan` and `terraform apply`?

Accepted Answer

`terraform plan` shows the proposed infrastructure changes without executing them. `terraform apply` performs the approved changes.

This separation is valuable because it supports review and safety. Teams can inspect the plan, understand the blast radius, and catch unintended changes before real resources are affected.

Question 5

What are modules in Terraform?

Accepted Answer

Modules are reusable units of Terraform configuration that package related resources and inputs into a consistent pattern.

Modules improve maintainability by reducing duplication and standardizing infrastructure design. For example, a team might create modules for VPCs, Kubernetes clusters, databases, or application services.

Question 6

What is drift in Terraform?

Accepted Answer

Drift occurs when the actual infrastructure changes outside Terraform or no longer matches the configuration and state Terraform expects.

Drift matters because it breaks the assumption that code describes reality. Good answers mention detecting drift through plans and reconciling it intentionally rather than blindly applying changes.

Question 7

Why is version pinning important in Terraform?

Accepted Answer

Version pinning helps control changes in Terraform itself, providers, and module behavior. It reduces unexpected breakage caused by new releases.

This is especially important in production automation, where even small provider behavior changes can affect plan results. Predictability is a major part of safe infrastructure management.

Question 8

What does `terraform init` do?

Accepted Answer

`terraform init` initializes a working directory by downloading providers, setting up backend configuration, and preparing modules.

It is typically the first command run in a Terraform workflow for a project or after changing backend or provider configuration. A good answer should show that you understand it is setup, not planning or applying.

Question 9

When would you use `taint` or `-replace`?

Accepted Answer

You use forced replacement when a resource must be recreated instead of updated in place, such as when it is corrupted, stuck, or needs a clean rebuild due to provider or platform limitations.

This should be done carefully because replacement may cause downtime or data loss depending on the resource. Strong answers mention understanding impact before forcing recreation.

Question 10

How do you manage secrets with Terraform?

Accepted Answer

Terraform should integrate with secret managers and avoid hardcoding sensitive values in configuration whenever possible.

It is also important to remember that sensitive values can still appear in state depending on the resource and provider. That is why backend security, state access control, and careful output handling are critical.

Question 11

How do you make Terraform changes safer in production?

Accepted Answer

I would use remote state with locking, require plan review, keep modules well tested, separate environments clearly, and avoid making unrelated infrastructure changes in one large apply.

Mature teams also use CI/CD validation, policy checks, and clear rollback or recovery thinking. Safe Terraform is as much about workflow discipline as it is about syntax.

Question 12

What makes a good Terraform codebase?

Accepted Answer

A good Terraform codebase is modular, readable, consistent, version-pinned, environment-aware, and designed to minimize accidental complexity.

It should be easy to review, easy to validate, and structured so teams understand ownership and change impact. Good Terraform is not just functional; it is maintainable and safe under collaboration.

Question 13

What is Infrastructure as Code?

Accepted Answer

Infrastructure as Code is the practice of defining and managing infrastructure through code files rather than manual changes in a UI or shell session.

It improves repeatability, reviewability, and automation. Terraform is one popular tool for this approach, but the core principle matters beyond any single product.

Question 14

Why is declarative infrastructure useful?

Accepted Answer

Declarative infrastructure describes the desired end state instead of every step needed to reach it.

This is useful because the tool can determine how to create or update resources based on the current state. It makes infrastructure management more predictable at scale.

Question 15

What is a provider in Terraform?

Accepted Answer

A provider is the plugin Terraform uses to interact with a platform or API such as AWS, Azure, GCP, Kubernetes, or GitHub.

Providers matter because they define the resource types and behaviors Terraform can manage. Good answers may mention version pinning and provider-specific quirks.

Question 16

What are input variables in Terraform?

Accepted Answer

Input variables let you parameterize Terraform configurations so the same code can be reused with different values.

They help reduce duplication and make modules more flexible. A strong answer may mention defaults, validation, and environment-specific values.

Question 17

What are outputs in Terraform?

Accepted Answer

Outputs expose useful values from a Terraform configuration, such as resource IDs, IP addresses, or endpoint URLs.

They help connect modules or make important information visible after apply. Good answers also mention being careful with sensitive outputs.

Question 18

What are locals in Terraform?

Accepted Answer

Locals are named expressions used to simplify repeated logic or improve readability within a Terraform configuration.

They are useful for keeping code cleaner when derived values are reused multiple times. This helps reduce duplication without turning everything into variables.

Question 19

Why is state locking important?

Accepted Answer

State locking prevents multiple Terraform operations from modifying the same state at the same time.

This matters because concurrent writes can corrupt state or produce dangerous race conditions. Remote backends that support locking are especially important in team environments.

Question 20

What is `terraform fmt` used for?

Accepted Answer

`terraform fmt` formats Terraform configuration files according to standard style rules.

It improves consistency and review quality. While it does not validate logic, it makes code easier to read and compare across teams.

Question 21

What is `terraform validate` used for?

Accepted Answer

`terraform validate` checks whether Terraform configuration is syntactically valid and internally consistent.

It is useful as a quick CI step before planning, but it does not replace plan review because it does not evaluate the real change impact on infrastructure.

Question 22

What is the purpose of workspaces in Terraform?

Accepted Answer

Workspaces allow multiple state instances for the same configuration, often used to separate environments.

They can be useful, but many teams prefer clearer environment separation using directories or repositories because workspaces can become confusing if overused.

Question 23

What is the `lifecycle` block in Terraform?

Accepted Answer

The `lifecycle` block lets you influence how Terraform handles certain resources, including behaviors like create-before-destroy or preventing destroy.

This can improve safety for sensitive resources, but it should be used thoughtfully. It changes how Terraform reconciles state and may affect risk during updates.

Question 24

What does `prevent_destroy` do?

Accepted Answer

`prevent_destroy` is a lifecycle setting that stops Terraform from accidentally destroying a resource unless the configuration is changed intentionally.

It is useful for critical resources such as important databases or foundational network components where accidental deletion would be costly.

Question 25

What is import in Terraform?

Accepted Answer

Import lets Terraform bring an existing real-world resource under Terraform state management.

This is helpful when teams adopt Terraform after infrastructure already exists, but importing safely requires care so configuration and actual resource settings align correctly.

Question 26

How do you review Terraform changes safely?

Accepted Answer

I would inspect the plan carefully, look for unexpected destroys or replacements, review module and variable changes, and consider environment-specific blast radius before approval.

Good Terraform review is not only about syntax. It is about understanding what the infrastructure will actually do after apply.

Question 27

How do you reduce Terraform drift and manual change risk?

Accepted Answer

I would keep infrastructure changes flowing through code review and pipelines, restrict manual console changes where practical, and monitor for unexpected drift regularly.

Drift is partly a tooling issue and partly a process issue. Strong practices reduce the chances that infrastructure diverges from its declared source of truth.

Question 28

What is state backend configuration?

Accepted Answer

Backend configuration tells Terraform where and how to store state, such as in cloud object storage with optional locking support.

It is foundational for team usage because backend design affects collaboration, recovery, and safety.

Question 29

What is the purpose of module version pinning?

Accepted Answer

Module version pinning prevents unexpected behavior changes from upstream module updates by locking usage to a known version.

This improves predictability and helps teams adopt changes intentionally instead of discovering them during a routine plan.

Question 30

Why should Terraform runs usually happen through CI/CD in teams?

Accepted Answer

Running Terraform through CI/CD improves consistency, reviewability, auditability, and control over who can change infrastructure.

It reduces the chance of ad-hoc local actions creating drift or bypassing team process. Mature Terraform workflows are usually pipeline-driven.

Infrastructure as Code (Terraform)

1. Why use Terraform in DevOps teams?

2. What is Terraform state, and why is it important?

3. Why should Terraform state usually be stored remotely?

4. What is the difference between `terraform plan` and `terraform apply`?

5. What are modules in Terraform?

6. What is drift in Terraform?

7. Why is version pinning important in Terraform?

8. What does `terraform init` do?

9. When would you use `taint` or `-replace`?

10. How do you manage secrets with Terraform?

11. How do you make Terraform changes safer in production?

12. What makes a good Terraform codebase?

13. What is Infrastructure as Code?

14. Why is declarative infrastructure useful?

15. What is a provider in Terraform?

16. What are input variables in Terraform?

17. What are outputs in Terraform?

18. What are locals in Terraform?

19. Why is state locking important?

20. What is `terraform fmt` used for?

21. What is `terraform validate` used for?

22. What is the purpose of workspaces in Terraform?

23. What is the `lifecycle` block in Terraform?

24. What does `prevent_destroy` do?

25. What is import in Terraform?

26. How do you review Terraform changes safely?

27. How do you reduce Terraform drift and manual change risk?

28. What is state backend configuration?

29. What is the purpose of module version pinning?

30. Why should Terraform runs usually happen through CI/CD in teams?