Positioning

This document does not invent an OpenTofu certification. OpenTofu is documented as a CNCF Sandbox project. The Linux Foundation offers an official free course, Getting Started with OpenTofu (LFEL1009). In the checked Linux Foundation certification catalog, this workshop does not treat any standalone OpenTofu core certification as a standard exam.

Important for this workshop:

• OpenTofu knowledge is practical for IaC, DevOps, platform and cloud roles.
• OpenTofu is closely related to Terraform-compatible workflows, but this workshop is written OpenTofu-first and points to OpenTofu documentation.
• This workshop develops practical competence: HCL, providers, state, backends, modules, CI/CD, security and incident response.

Competency Mapping

Preparation Without Exam Claims

1. Check current OpenTofu, CNCF and Linux Foundation pages.
2. Compare official training objectives with the workshop levels.
3. Practice real local configurations, state models and review artifacts.
4. Document gaps before booking an external provider exam.
5. Use this workshop's assessments as internal readiness checks, not as a replacement for provider material.

Review Checklist for OpenTofu Certificate Preparation

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

Practice Appendix: OpenTofu Certificate Preparation

This appendix provides a backlog for longer trainings, reviews and repetition. Each task is small enough to verify with local HCL artifacts and a Git repository.

A001. OpenTofu

• Task: document configuration and desired state and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A002. HCL

• Task: check provider requirement and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A003. Provider

• Task: explain state impact and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A004. State

• Task: assess plan diff and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A005. Backend

• Task: describe backend and locking model and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A006. Module

• Task: check module boundary and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A007. Plan

• Task: assess variable and output and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A008. Apply

• Task: prove drift and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A009. TACOS

• Task: mark secret risk and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A010. Security

• Task: name policy or CI gate and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A011. OpenTofu

• Task: write down rollback or recovery path and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A012. HCL

• Task: state a team rule and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A013. Provider

• Task: document configuration and desired state and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A014. State

• Task: check provider requirement and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A015. Backend

• Task: explain state impact and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A016. Module

• Task: assess plan diff and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A017. Plan

• Task: describe backend and locking model and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A018. Apply

• Task: check module boundary and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A019. TACOS

• Task: assess variable and output and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A020. Security

• Task: prove drift and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A021. OpenTofu

• Task: mark secret risk and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A022. HCL

• Task: name policy or CI gate and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A023. Provider

• Task: write down rollback or recovery path and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A024. State

• Task: state a team rule and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A025. Backend

• Task: document configuration and desired state and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A026. Module

• Task: check provider requirement and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A027. Plan

• Task: explain state impact and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A028. Apply

• Task: assess plan diff and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A029. TACOS

• Task: describe backend and locking model and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A030. Security

• Task: check module boundary and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A031. OpenTofu

• Task: assess variable and output and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A032. HCL

• Task: prove drift and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A033. Provider

• Task: mark secret risk and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A034. State

• Task: name policy or CI gate and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A035. Backend

• Task: write down rollback or recovery path and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A036. Module

• Task: state a team rule and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A037. Plan

• Task: document configuration and desired state and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A038. Apply

• Task: check provider requirement and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A039. TACOS

• Task: explain state impact and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A040. Security

• Task: assess plan diff and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A041. OpenTofu

• Task: describe backend and locking model and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A042. HCL

• Task: check module boundary and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A043. Provider

• Task: assess variable and output and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A044. State

• Task: prove drift and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A045. Backend

• Task: mark secret risk and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A046. Module

• Task: name policy or CI gate and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A047. Plan

• Task: write down rollback or recovery path and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A048. Apply

• Task: state a team rule and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A049. TACOS

• Task: document configuration and desired state and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A050. Security

• Task: check provider requirement and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A051. OpenTofu

• Task: explain state impact and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A052. HCL

• Task: assess plan diff and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A053. Provider

• Task: describe backend and locking model and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A054. State

• Task: check module boundary and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A055. Backend

• Task: assess variable and output and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A056. Module

• Task: prove drift and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A057. Plan

• Task: mark secret risk and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A058. Apply

• Task: name policy or CI gate and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A059. TACOS

• Task: write down rollback or recovery path and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A060. Security

• Task: state a team rule and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A061. OpenTofu

• Task: document configuration and desired state and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A062. HCL

• Task: check provider requirement and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A063. Provider

• Task: explain state impact and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A064. State

• Task: assess plan diff and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A065. Backend

• Task: describe backend and locking model and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A066. Module

• Task: check module boundary and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A067. Plan

• Task: assess variable and output and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A068. Apply

• Task: prove drift and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A069. TACOS

• Task: mark secret risk and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A070. Security

• Task: name policy or CI gate and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A071. OpenTofu

• Task: write down rollback or recovery path and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A072. HCL

• Task: state a team rule and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A073. Provider

• Task: document configuration and desired state and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A074. State

• Task: check provider requirement and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A075. Backend

• Task: explain state impact and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A076. Module

• Task: assess plan diff and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A077. Plan

• Task: describe backend and locking model and explicitly relate the observation to Plan.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A078. Apply

• Task: check module boundary and explicitly relate the observation to Apply.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A079. TACOS

• Task: assess variable and output and explicitly relate the observation to TACOS.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A080. Security

• Task: prove drift and explicitly relate the observation to Security.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A081. OpenTofu

• Task: mark secret risk and explicitly relate the observation to OpenTofu.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A082. HCL

• Task: name policy or CI gate and explicitly relate the observation to HCL.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A083. Provider

• Task: write down rollback or recovery path and explicitly relate the observation to Provider.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A084. State

• Task: state a team rule and explicitly relate the observation to State.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A085. Backend

• Task: document configuration and desired state and explicitly relate the observation to Backend.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

A086. Module

• Task: check provider requirement and explicitly relate the observation to Module.
• Evidence: Write down at least one OpenTofu-adjacent command, one expected result and one limit of that evidence.
• Operations question: What would a wrong assumption change in dev, staging, prod and CI?
• Security question: Which credentials, state values, provider versions or outputs would be critical?
• Recovery: Explain whether revert, state operation, import, backend restore, secret rotation or manual provider correction is required.

Official Sources and Scope

The material is aligned with public OpenTofu documentation. Cloud providers, TACOS platforms, policy engines and secret tools are mentioned only where they explain common OpenTofu workflows. Example artifacts are not instructions to execute against production cloud accounts.

• OpenTofu: https://opentofu.org/
• OpenTofu Language Documentation: https://opentofu.org/docs/language/
• Provider Requirements: https://opentofu.org/docs/language/providers/requirements/
• State: https://opentofu.org/docs/language/state/
• Backend Configuration: https://opentofu.org/docs/language/settings/backends/configuration/
• OpenTofu v1.x Compatibility Promises: https://opentofu.org/docs/language/v1-compatibility-promises/
• OpenTofu at CNCF: https://www.cncf.io/projects/opentofu/
• Linux Foundation: Getting Started with OpenTofu: https://training.linuxfoundation.org/express-learning/getting-started-with-opentofu-lfel1009/
• Linux Foundation Certification Catalog: https://training.linuxfoundation.org/certification-catalog/

Additional Review Drills

Use these drills when the primary task is complete and the learner needs another pass over operational reasoning. They are intentionally evidence-oriented and can be answered with local OpenTofu artifacts.

Drill 01: root module

• State which module, provider, backend or state boundary is affected by root module.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 02: provider version

• State which module, provider, backend or state boundary is affected by provider version.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 03: state snapshot

• State which module, provider, backend or state boundary is affected by state snapshot.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 04: backend locking

• State which module, provider, backend or state boundary is affected by backend locking.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 05: plan diff

• State which module, provider, backend or state boundary is affected by plan diff.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 06: module output

• State which module, provider, backend or state boundary is affected by module output.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 07: sensitive value

• State which module, provider, backend or state boundary is affected by sensitive value.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 08: policy gate

• State which module, provider, backend or state boundary is affected by policy gate.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 09: import

• State which module, provider, backend or state boundary is affected by import.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 10: moved block

• State which module, provider, backend or state boundary is affected by moved block.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 11: TACOS run

• State which module, provider, backend or state boundary is affected by TACOS run.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 12: recovery

• State which module, provider, backend or state boundary is affected by recovery.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 13: root module

• State which module, provider, backend or state boundary is affected by root module.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 14: provider version

• State which module, provider, backend or state boundary is affected by provider version.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 15: state snapshot

• State which module, provider, backend or state boundary is affected by state snapshot.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.

Drill 16: backend locking

• State which module, provider, backend or state boundary is affected by backend locking.
• Name one command or HCL field that produces evidence.
• Explain what can be concluded from that evidence and what cannot be concluded from it.
• Describe the safest recovery path for a shared IaC platform.