Format

• written questions
• practical HCL task
• review of a risky Terraform scenario
• short operations and security assessment

Notes

Work without production credentials. Document assumptions. If Terraform is missing locally, record that and run at least static structure checks.

Questions

Question 01

Explain how you classify IaC and Terraform. Name at least one command, one error case, one state or plan impact and one security risk.

Question 02

Explain how you read and structure HCL files. Name at least one command, one error case, one state or plan impact and one security risk.

Question 03

Explain how you declare provider requirements. Name at least one command, one error case, one state or plan impact and one security risk.

Question 04

Explain how you review provider versions and lock files. Name at least one command, one error case, one state or plan impact and one security risk.

Question 05

Explain how you distinguish resources and data sources. Name at least one command, one error case, one state or plan impact and one security risk.

Question 06

Explain how you model variables, locals and outputs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 07

Explain how you run the Terraform workflow. Name at least one command, one error case, one state or plan impact and one security risk.

Question 08

Explain how you review plan diffs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 09

Explain how you explain state bindings. Name at least one command, one error case, one state or plan impact and one security risk.

Question 10

Explain how you design backends and locking. Name at least one command, one error case, one state or plan impact and one security risk.

Question 11

Explain how you shape modules with inputs and outputs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 12

Explain how you apply for_each, count and dynamic blocks. Name at least one command, one error case, one state or plan impact and one security risk.

Question 13

Explain how you evaluate lifecycle meta-arguments. Name at least one command, one error case, one state or plan impact and one security risk.

Question 14

Explain how you differentiate workspaces and environment layouts. Name at least one command, one error case, one state or plan impact and one security risk.

Question 15

Explain how you plan imports and moved blocks. Name at least one command, one error case, one state or plan impact and one security risk.

Question 16

Explain how you use remote state responsibly. Name at least one command, one error case, one state or plan impact and one security risk.

Question 17

Explain how you make CI/CD plan artifacts reviewable. Name at least one command, one error case, one state or plan impact and one security risk.

Question 18

Explain how you model policy as code as a gate. Name at least one command, one error case, one state or plan impact and one security risk.

Question 19

Explain how you protect secrets and sensitive values. Name at least one command, one error case, one state or plan impact and one security risk.

Question 20

Explain how you detect and handle drift. Name at least one command, one error case, one state or plan impact and one security risk.

Question 21

Explain how you classify HCP Terraform and Terraform Enterprise. Name at least one command, one error case, one state or plan impact and one security risk.

Question 22

Explain how you review supply-chain risks from providers and modules. Name at least one command, one error case, one state or plan impact and one security risk.

Question 23

Explain how you plan destroy protection and recovery. Name at least one command, one error case, one state or plan impact and one security risk.

Question 24

Explain how you run incident response for state or credential leaks. Name at least one command, one error case, one state or plan impact and one security risk.

Question 25

Explain how you classify IaC and Terraform. Name at least one command, one error case, one state or plan impact and one security risk.

Question 26

Explain how you read and structure HCL files. Name at least one command, one error case, one state or plan impact and one security risk.

Question 27

Explain how you declare provider requirements. Name at least one command, one error case, one state or plan impact and one security risk.

Question 28

Explain how you review provider versions and lock files. Name at least one command, one error case, one state or plan impact and one security risk.

Question 29

Explain how you distinguish resources and data sources. Name at least one command, one error case, one state or plan impact and one security risk.

Question 30

Explain how you model variables, locals and outputs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 31

Explain how you run the Terraform workflow. Name at least one command, one error case, one state or plan impact and one security risk.

Question 32

Explain how you review plan diffs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 33

Explain how you explain state bindings. Name at least one command, one error case, one state or plan impact and one security risk.

Question 34

Explain how you design backends and locking. Name at least one command, one error case, one state or plan impact and one security risk.

Question 35

Explain how you shape modules with inputs and outputs. Name at least one command, one error case, one state or plan impact and one security risk.

Question 36

Explain how you apply for_each, count and dynamic blocks. Name at least one command, one error case, one state or plan impact and one security risk.

Question 37

Explain how you evaluate lifecycle meta-arguments. Name at least one command, one error case, one state or plan impact and one security risk.

Question 38

Explain how you differentiate workspaces and environment layouts. Name at least one command, one error case, one state or plan impact and one security risk.

Question 39

Explain how you plan imports and moved blocks. Name at least one command, one error case, one state or plan impact and one security risk.

Question 40

Explain how you use remote state responsibly. Name at least one command, one error case, one state or plan impact and one security risk.

Question 41

Explain how you make CI/CD plan artifacts reviewable. Name at least one command, one error case, one state or plan impact and one security risk.

Question 42

Explain how you model policy as code as a gate. Name at least one command, one error case, one state or plan impact and one security risk.

Question 43

Explain how you protect secrets and sensitive values. Name at least one command, one error case, one state or plan impact and one security risk.

Question 44

Explain how you detect and handle drift. Name at least one command, one error case, one state or plan impact and one security risk.

Question 45

Explain how you classify HCP Terraform and Terraform Enterprise. Name at least one command, one error case, one state or plan impact and one security risk.

Question 46

Explain how you review supply-chain risks from providers and modules. Name at least one command, one error case, one state or plan impact and one security risk.

Question 47

Explain how you plan destroy protection and recovery. Name at least one command, one error case, one state or plan impact and one security risk.

Question 48

Explain how you run incident response for state or credential leaks. Name at least one command, one error case, one state or plan impact and one security risk.

Practical Task

Create a small root module with variables, locals, resources, output, provider pinning and review note. Add backend and recovery assessment.

Review Checklist for Professional

• 01. document configuration and target state: Record the affected module, provider, resource, state and backend path.
• 02. review provider requirement: Record the affected module, provider, resource, state and backend path.
• 03. explain state impact: Record the affected module, provider, resource, state and backend path.
• 04. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
• 05. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
• 06. review module boundary: Record the affected module, provider, resource, state and backend path.
• 07. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
• 08. produce drift evidence: Record the affected module, provider, resource, state and backend path.
• 09. mark secret risk: Record the affected module, provider, resource, state and backend path.
• 10. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
• 11. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
• 12. write team rule: Record the affected module, provider, resource, state and backend path.
• 13. document configuration and target state: Record the affected module, provider, resource, state and backend path.
• 14. review provider requirement: Record the affected module, provider, resource, state and backend path.
• 15. explain state impact: Record the affected module, provider, resource, state and backend path.
• 16. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
• 17. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
• 18. review module boundary: Record the affected module, provider, resource, state and backend path.
• 19. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
• 20. produce drift evidence: Record the affected module, provider, resource, state and backend path.
• 21. mark secret risk: Record the affected module, provider, resource, state and backend path.
• 22. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
• 23. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
• 24. write team rule: Record the affected module, provider, resource, state and backend path.
• 25. document configuration and target state: Record the affected module, provider, resource, state and backend path.
• 26. review provider requirement: Record the affected module, provider, resource, state and backend path.
• 27. explain state impact: Record the affected module, provider, resource, state and backend path.
• 28. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
• 29. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
• 30. review module boundary: Record the affected module, provider, resource, state and backend path.
• 31. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
• 32. produce drift evidence: Record the affected module, provider, resource, state and backend path.
• 33. mark secret risk: Record the affected module, provider, resource, state and backend path.
• 34. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
• 35. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
• 36. write team rule: Record the affected module, provider, resource, state and backend path.
• 37. document configuration and target state: Record the affected module, provider, resource, state and backend path.
• 38. review provider requirement: Record the affected module, provider, resource, state and backend path.
• 39. explain state impact: Record the affected module, provider, resource, state and backend path.
• 40. evaluate plan diff: Record the affected module, provider, resource, state and backend path.
• 41. describe backend and locking model: Record the affected module, provider, resource, state and backend path.
• 42. review module boundary: Record the affected module, provider, resource, state and backend path.
• 43. evaluate variable and output: Record the affected module, provider, resource, state and backend path.
• 44. produce drift evidence: Record the affected module, provider, resource, state and backend path.
• 45. mark secret risk: Record the affected module, provider, resource, state and backend path.

Practice Appendix: Professional

This appendix is a working backlog for longer trainings, reviews and repetitions. Each task can be checked locally with HCL artifacts and a Git repository.

A001. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A002. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A003. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A004. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A005. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A006. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A007. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A008. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A009. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A010. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A011. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A012. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A013. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A014. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A015. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A016. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A017. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A018. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A019. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A020. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A021. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A022. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A023. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A024. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A025. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A026. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A027. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A028. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A029. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A030. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A031. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A032. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A033. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A034. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A035. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A036. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A037. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A038. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A039. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A040. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A041. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A042. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A043. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A044. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A045. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A046. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A047. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A048. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A049. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A050. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A051. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A052. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A053. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A054. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A055. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A056. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A057. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A058. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A059. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A060. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A061. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A062. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A063. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A064. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A065. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A066. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A067. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A068. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A069. Terraform

• Task: mark secret risk and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A070. Review

• Task: name policy or CI gate and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A071. State

• Task: record rollback or recovery path and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A072. Security

• Task: write team rule and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A073. Terraform

• Task: document configuration and target state and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A074. Review

• Task: review provider requirement and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A075. State

• Task: explain state impact and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A076. Security

• Task: evaluate plan diff and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A077. Terraform

• Task: describe backend and locking model and connect the observation explicitly to Terraform.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A078. Review

• Task: review module boundary and connect the observation explicitly to Review.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A079. State

• Task: evaluate variable and output and connect the observation explicitly to State.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.

A080. Security

• Task: produce drift evidence and connect the observation explicitly to Security.
• Evidence: Record at least one Terraform-related command, expected output and a boundary of that evidence.
• Operations question: What would a wrong assumption cause in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Describe whether revert, state operation, import, backend restore, secret rotation or manual provider correction would be needed.