OpenTofu Solution: Fundamentals (EN)

This solution guide belongs to the assessment Fundamentals. It does not provide one rigid answer; it defines verifiable answer criteria.

Grading Rubric

Area	Expectation
Terms	Configuration, provider, resource, state, backend, plan and apply are separated cleanly.
Evidence	Answers name HCL locations, CLI commands, state impact and review artifacts.
Operations	Backend, locking, drift, modules, CI and TACOS are covered.
Security	State, secrets, provider pinning, credentials and supply chain are assessed.

Sample Criteria

Solution 01: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 02: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 03: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 04: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 05: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 06: Outputs

A strong answer for Outputs names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 07: Plan und Apply

A strong answer for Plan und Apply names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 08: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 09: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 10: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 11: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 12: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 13: Outputs

A strong answer for Outputs names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 14: Plan und Apply

A strong answer for Plan und Apply names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 15: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 16: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 17: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 18: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 19: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 20: Outputs

A strong answer for Outputs names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 21: Plan und Apply

A strong answer for Plan und Apply names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 22: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 23: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 24: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 25: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 26: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 27: Outputs

A strong answer for Outputs names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 28: Plan und Apply

A strong answer for Plan und Apply names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 29: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 30: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 31: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 32: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 33: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 34: Outputs

A strong answer for Outputs names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 35: Plan und Apply

A strong answer for Plan und Apply names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 36: OpenTofu CLI

A strong answer for OpenTofu CLI names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 37: HCL

A strong answer for HCL names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 38: Ressourcen

A strong answer for Ressourcen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 39: Provider

A strong answer for Provider names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Solution 40: Variablen

A strong answer for Variablen names root module, provider, state impact, backend and concrete recovery path.

Good evidence: HCL excerpt, tofu validate, plan diff, state list, output assessment or backend configuration.
Common mistake: treating state as a harmless cache file or calling sensitive values safe only because they are masked.
Security expectation: no real secrets, remote state with access control, provider pinning, review gates and documented incident response.

Practice Appendix: Fundamentals Solution

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 CLI

Task: document configuration and desired state and explicitly relate the observation to OpenTofu CLI.
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. Ressourcen

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

Task: assess plan diff 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.

A005. Variablen

Task: describe backend and locking model and explicitly relate the observation to Variablen.
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. Outputs

Task: check module boundary and explicitly relate the observation to Outputs.
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 und Apply

Task: assess variable and output and explicitly relate the observation to Plan und 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.

A008. OpenTofu

Task: prove drift 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.

A009. Configuration

Task: mark secret risk and explicitly relate the observation to Configuration.
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. Root Module

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

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

A012. Resource

Task: state a team rule and explicitly relate the observation to Resource.
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. Data Source

Task: document configuration and desired state and explicitly relate the observation to Data Source.
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. Variable

Task: check provider requirement and explicitly relate the observation to Variable.
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. Output

Task: explain state impact and explicitly relate the observation to Output.
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. Local Value

Task: assess plan diff and explicitly relate the observation to Local Value.
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. State

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

A018. Backend

Task: check module boundary 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.

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

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

A021. Module

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

A022. Meta-Argument

Task: name policy or CI gate and explicitly relate the observation to Meta-Argument.
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. 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.

A024. OpenTofu CLI

Task: state a team rule and explicitly relate the observation to OpenTofu CLI.
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. HCL

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

A026. Ressourcen

Task: check provider requirement and explicitly relate the observation to Ressourcen.
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. 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.

A028. Variablen

Task: assess plan diff and explicitly relate the observation to Variablen.
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. Outputs

Task: describe backend and locking model and explicitly relate the observation to Outputs.
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. Plan und Apply

Task: check module boundary and explicitly relate the observation to Plan und 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.

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

Task: prove drift and explicitly relate the observation to Configuration.
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. Root Module

Task: mark secret risk and explicitly relate the observation to Root 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.

A034. Provider

Task: name policy or CI gate 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.

A035. Resource

Task: write down rollback or recovery path and explicitly relate the observation to Resource.
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. Data Source

Task: state a team rule and explicitly relate the observation to Data Source.
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. Variable

Task: document configuration and desired state and explicitly relate the observation to Variable.
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. Output

Task: check provider requirement and explicitly relate the observation to Output.
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. Local Value

Task: explain state impact and explicitly relate the observation to Local Value.
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. 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.

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

A042. Plan

Task: check module boundary 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.

A043. Apply

Task: assess variable and output 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.

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

A045. Meta-Argument

Task: mark secret risk and explicitly relate the observation to Meta-Argument.
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. TACOS

Task: name policy or CI gate 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.

A047. OpenTofu CLI

Task: write down rollback or recovery path and explicitly relate the observation to OpenTofu CLI.
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. 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.

A049. Ressourcen

Task: document configuration and desired state and explicitly relate the observation to Ressourcen.
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. Provider

Task: check provider requirement 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.

A051. Variablen

Task: explain state impact and explicitly relate the observation to Variablen.
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. Outputs

Task: assess plan diff and explicitly relate the observation to Outputs.
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. Plan und Apply

Task: describe backend and locking model and explicitly relate the observation to Plan und 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.

A054. OpenTofu

Task: check module boundary 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.

A055. Configuration

Task: assess variable and output and explicitly relate the observation to Configuration.
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. Root Module

Task: prove drift and explicitly relate the observation to Root 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. 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.

A058. Resource

Task: name policy or CI gate and explicitly relate the observation to Resource.
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. Data Source

Task: write down rollback or recovery path and explicitly relate the observation to Data Source.
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. Variable

Task: state a team rule and explicitly relate the observation to Variable.
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. Output

Task: document configuration and desired state and explicitly relate the observation to Output.
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. Local Value

Task: check provider requirement and explicitly relate the observation to Local Value.
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. State

Task: explain state impact 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.

A064. Backend

Task: assess plan diff 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.

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

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

A067. Module

Task: assess variable and output 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.

A068. Meta-Argument

Task: prove drift and explicitly relate the observation to Meta-Argument.
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. OpenTofu CLI

Task: name policy or CI gate and explicitly relate the observation to OpenTofu CLI.
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. HCL

Task: write down rollback or recovery path 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.

A072. Ressourcen

Task: state a team rule and explicitly relate the observation to Ressourcen.
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. Variablen

Task: check provider requirement and explicitly relate the observation to Variablen.
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.

OpenTofu Solution: Fundamentals (EN)

Grading Rubric

Sample Criteria

Solution 01: OpenTofu CLI

Solution 02: HCL

Solution 03: Ressourcen

Solution 04: Provider

Solution 05: Variablen

Solution 06: Outputs

Solution 07: Plan und Apply

Solution 08: OpenTofu CLI

Solution 09: HCL

Solution 10: Ressourcen

Solution 11: Provider

Solution 12: Variablen

Solution 13: Outputs

Solution 14: Plan und Apply

Solution 15: OpenTofu CLI

Solution 16: HCL

Solution 17: Ressourcen

Solution 18: Provider

Solution 19: Variablen

Solution 20: Outputs

Solution 21: Plan und Apply

Solution 22: OpenTofu CLI

Solution 23: HCL

Solution 24: Ressourcen

Solution 25: Provider

Solution 26: Variablen

Solution 27: Outputs

Solution 28: Plan und Apply

Solution 29: OpenTofu CLI

Solution 30: HCL

Solution 31: Ressourcen

Solution 32: Provider

Solution 33: Variablen

Solution 34: Outputs

Solution 35: Plan und Apply

Solution 36: OpenTofu CLI

Solution 37: HCL

Solution 38: Ressourcen

Solution 39: Provider

Solution 40: Variablen

Review Checklist for Fundamentals Solution

Practice Appendix: Fundamentals Solution

A001. OpenTofu CLI

A002. HCL

A003. Ressourcen

A004. Provider

A005. Variablen

A006. Outputs

A007. Plan und Apply

A008. OpenTofu

A009. Configuration

A010. Root Module

A011. Provider

A012. Resource

A013. Data Source

A014. Variable

A015. Output

A016. Local Value

A017. State

A018. Backend

A019. Plan

A020. Apply

A021. Module

A022. Meta-Argument

A023. TACOS

A024. OpenTofu CLI

A025. HCL

A026. Ressourcen

A027. Provider

A028. Variablen

A029. Outputs

A030. Plan und Apply

A031. OpenTofu

A032. Configuration

A033. Root Module

A034. Provider

A035. Resource