Submission Format

• HCL files or patch
• sample values used
• commands or static checks executed
• expected plan or state impact
• short risk and recovery note

Tasks

Task 01: HCL

Build or improve a Terraform artifact focused on HCL.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 02: Provider

Build or improve a Terraform artifact focused on Provider.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 03: State

Build or improve a Terraform artifact focused on State.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 04: Backend

Build or improve a Terraform artifact focused on Backend.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 05: Module

Build or improve a Terraform artifact focused on Module.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 06: for_each

Build or improve a Terraform artifact focused on for_each.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 07: Import

Build or improve a Terraform artifact focused on Import.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 08: Policy

Build or improve a Terraform artifact focused on Policy.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 09: Secrets

Build or improve a Terraform artifact focused on Secrets.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 10: Drift

Build or improve a Terraform artifact focused on Drift.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 11: HCL

Build or improve a Terraform artifact focused on HCL.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 12: Provider

Build or improve a Terraform artifact focused on Provider.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 13: State

Build or improve a Terraform artifact focused on State.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 14: Backend

Build or improve a Terraform artifact focused on Backend.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 15: Module

Build or improve a Terraform artifact focused on Module.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 16: for_each

Build or improve a Terraform artifact focused on for_each.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 17: Import

Build or improve a Terraform artifact focused on Import.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 18: Policy

Build or improve a Terraform artifact focused on Policy.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 19: Secrets

Build or improve a Terraform artifact focused on Secrets.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 20: Drift

Build or improve a Terraform artifact focused on Drift.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 21: HCL

Build or improve a Terraform artifact focused on HCL.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 22: Provider

Build or improve a Terraform artifact focused on Provider.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 23: State

Build or improve a Terraform artifact focused on State.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 24: Backend

Build or improve a Terraform artifact focused on Backend.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 25: Module

Build or improve a Terraform artifact focused on Module.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 26: for_each

Build or improve a Terraform artifact focused on for_each.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 27: Import

Build or improve a Terraform artifact focused on Import.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 28: Policy

Build or improve a Terraform artifact focused on Policy.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 29: Secrets

Build or improve a Terraform artifact focused on Secrets.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 30: Drift

Build or improve a Terraform artifact focused on Drift.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 31: HCL

Build or improve a Terraform artifact focused on HCL.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 32: Provider

Build or improve a Terraform artifact focused on Provider.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 33: State

Build or improve a Terraform artifact focused on State.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 34: Backend

Build or improve a Terraform artifact focused on Backend.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 35: Module

Build or improve a Terraform artifact focused on Module.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Task 36: for_each

Build or improve a Terraform artifact focused on for_each.

Requirements:

• do not use production credentials
• declare provider requirements
• describe state impact
• name an error or abuse path

Evidence:

terraform fmt -check -recursive || true
terraform init -backend=false || true
terraform validate || true

Solution Notes

Use local provider patterns, small modules and clear variables. Review not only syntax, but also state, backend, provider versions and recovery.

Review Checklist for Exercises Fundamentals

• 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.
• 46. name policy or CI gate: Record the affected module, provider, resource, state and backend path.
• 47. record rollback or recovery path: Record the affected module, provider, resource, state and backend path.
• 48. write team rule: Record the affected module, provider, resource, state and backend path.
• 49. document configuration and target state: Record the affected module, provider, resource, state and backend path.
• 50. review provider requirement: Record the affected module, provider, resource, state and backend path.

Practice Appendix: Exercises Fundamentals

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. HCL

• Task: document configuration and target state and connect the observation explicitly to HCL.
• 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. Provider

• Task: review provider requirement and connect the observation explicitly to Provider.
• 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. Backend

• Task: evaluate plan diff and connect the observation explicitly to Backend.
• 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. Module

• Task: describe backend and locking model and connect the observation explicitly to Module.
• 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. for_each

• Task: review module boundary and connect the observation explicitly to for_each.
• 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. Import

• Task: evaluate variable and output and connect the observation explicitly to Import.
• 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. Policy

• Task: produce drift evidence and connect the observation explicitly to Policy.
• 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. Secrets

• Task: mark secret risk and connect the observation explicitly to Secrets.
• 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. Drift

• Task: name policy or CI gate and connect the observation explicitly to Drift.
• 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. HCL

• Task: record rollback or recovery path and connect the observation explicitly to HCL.
• 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. Provider

• Task: write team rule and connect the observation explicitly to Provider.
• 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. State

• Task: document configuration and target state 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.

A014. Backend

• Task: review provider requirement and connect the observation explicitly to Backend.
• 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. Module

• Task: explain state impact and connect the observation explicitly to Module.
• 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. for_each

• Task: evaluate plan diff and connect the observation explicitly to for_each.
• 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. Import

• Task: describe backend and locking model and connect the observation explicitly to Import.
• 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. Policy

• Task: review module boundary and connect the observation explicitly to Policy.
• 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. Secrets

• Task: evaluate variable and output and connect the observation explicitly to Secrets.
• 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. Drift

• Task: produce drift evidence and connect the observation explicitly to Drift.
• 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. HCL

• Task: mark secret risk and connect the observation explicitly to HCL.
• 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. Provider

• Task: name policy or CI gate and connect the observation explicitly to Provider.
• 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. Backend

• Task: write team rule and connect the observation explicitly to Backend.
• 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. Module

• Task: document configuration and target state and connect the observation explicitly to Module.
• 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. for_each

• Task: review provider requirement and connect the observation explicitly to for_each.
• 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. Import

• Task: explain state impact and connect the observation explicitly to Import.
• 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. Policy

• Task: evaluate plan diff and connect the observation explicitly to Policy.
• 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. Secrets

• Task: describe backend and locking model and connect the observation explicitly to Secrets.
• 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. Drift

• Task: review module boundary and connect the observation explicitly to Drift.
• 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. HCL

• Task: evaluate variable and output and connect the observation explicitly to HCL.
• 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. Provider

• Task: produce drift evidence and connect the observation explicitly to Provider.
• 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. State

• Task: mark secret risk 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.

A034. Backend

• Task: name policy or CI gate and connect the observation explicitly to Backend.
• 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. Module

• Task: record rollback or recovery path and connect the observation explicitly to Module.
• 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. for_each

• Task: write team rule and connect the observation explicitly to for_each.
• 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. Import

• Task: document configuration and target state and connect the observation explicitly to Import.
• 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. Policy

• Task: review provider requirement and connect the observation explicitly to Policy.
• 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. Secrets

• Task: explain state impact and connect the observation explicitly to Secrets.
• 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. Drift

• Task: evaluate plan diff and connect the observation explicitly to Drift.
• 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. HCL

• Task: describe backend and locking model and connect the observation explicitly to HCL.
• 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. Provider

• Task: review module boundary and connect the observation explicitly to Provider.
• 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. Backend

• Task: produce drift evidence and connect the observation explicitly to Backend.
• 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. Module

• Task: mark secret risk and connect the observation explicitly to Module.
• 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. for_each

• Task: name policy or CI gate and connect the observation explicitly to for_each.
• 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. Import

• Task: record rollback or recovery path and connect the observation explicitly to Import.
• 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. Policy

• Task: write team rule and connect the observation explicitly to Policy.
• 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. Secrets

• Task: document configuration and target state and connect the observation explicitly to Secrets.
• 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. Drift

• Task: review provider requirement and connect the observation explicitly to Drift.
• 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. HCL

• Task: explain state impact and connect the observation explicitly to HCL.
• 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. Provider

• Task: evaluate plan diff and connect the observation explicitly to Provider.
• 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. State

• Task: describe backend and locking model 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.

A054. Backend

• Task: review module boundary and connect the observation explicitly to Backend.
• 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. Module

• Task: evaluate variable and output and connect the observation explicitly to Module.
• 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. for_each

• Task: produce drift evidence and connect the observation explicitly to for_each.
• 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. Import

• Task: mark secret risk and connect the observation explicitly to Import.
• 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. Policy

• Task: name policy or CI gate and connect the observation explicitly to Policy.
• 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. Secrets

• Task: record rollback or recovery path and connect the observation explicitly to Secrets.
• 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. Drift

• Task: write team rule and connect the observation explicitly to Drift.
• 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. HCL

• Task: document configuration and target state and connect the observation explicitly to HCL.
• 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. Provider

• Task: review provider requirement and connect the observation explicitly to Provider.
• 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. Backend

• Task: evaluate plan diff and connect the observation explicitly to Backend.
• 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. Module

• Task: describe backend and locking model and connect the observation explicitly to Module.
• 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. for_each

• Task: review module boundary and connect the observation explicitly to for_each.
• 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. Import

• Task: evaluate variable and output and connect the observation explicitly to Import.
• 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. Policy

• Task: produce drift evidence and connect the observation explicitly to Policy.
• 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. Secrets

• Task: mark secret risk and connect the observation explicitly to Secrets.
• 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. Drift

• Task: name policy or CI gate and connect the observation explicitly to Drift.
• 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. HCL

• Task: record rollback or recovery path and connect the observation explicitly to HCL.
• 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. Provider

• Task: write team rule and connect the observation explicitly to Provider.
• 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. State

• Task: document configuration and target state 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.

A074. Backend

• Task: review provider requirement and connect the observation explicitly to Backend.
• 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. Module

• Task: explain state impact and connect the observation explicitly to Module.
• 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. for_each

• Task: evaluate plan diff and connect the observation explicitly to for_each.
• 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. Import

• Task: describe backend and locking model and connect the observation explicitly to Import.
• 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. Policy

• Task: review module boundary and connect the observation explicitly to Policy.
• 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. Secrets

• Task: evaluate variable and output and connect the observation explicitly to Secrets.
• 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. Drift

• Task: produce drift evidence and connect the observation explicitly to Drift.
• 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.

A081. HCL

• Task: mark secret risk and connect the observation explicitly to HCL.
• 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.

A082. Provider

• Task: name policy or CI gate and connect the observation explicitly to Provider.
• 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.

A083. 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.

A084. Backend

• Task: write team rule and connect the observation explicitly to Backend.
• 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.

A085. Module

• Task: document configuration and target state and connect the observation explicitly to Module.
• 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.

A086. for_each

• Task: review provider requirement and connect the observation explicitly to for_each.
• 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.

A087. Import

• Task: explain state impact and connect the observation explicitly to Import.
• 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.

A088. Policy

• Task: evaluate plan diff and connect the observation explicitly to Policy.
• 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.

A089. Secrets

• Task: describe backend and locking model and connect the observation explicitly to Secrets.
• 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.

A090. Drift

• Task: review module boundary and connect the observation explicitly to Drift.
• 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.