Orthevs Orthevs Fathom new horizons
Menu

Workshop wiki · English

OpenTofu Exercises: Intermediate (EN)

These exercises belong to the workshop level Intermediate. Every task requires traceable evidence: root module, provider, desired state, state impact, backend relationship, risk and recovery path.

Content language · EnglishSize · 72.6 KBexercises/02-intermediate-exercises-opentofu-EN.md
Workshop examples as ZIP files
Learning progress in the web app

Mark chapters as read, view reading progress and check off practice modules after enabling the optional web app. Workshop progress is calculated from chapters across all document pages. Your choices stay on this device; there is no account or server sync. Installation is not required. Withdrawing your choice in Privacy settings deletes the progress.

Reading progress0%
0%
0 / 6 chapters read
Other language versionGerman ↗Greek ↗

OpenTofu Exercises: Intermediate (EN)

These exercises belong to the workshop level Intermediate. Every task requires traceable evidence: root module, provider, desired state, state impact, backend relationship, risk and recovery path.

Submission Format

Do not store production secrets. Document commands, relevant HCL excerpts, affected modules, plan/state impact, backend and security assessment, and recovery paths.

01 / 06

Required Tasks

Task 01: State

Goal: Examine State in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 02: Backends

Goal: Examine Backends in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 03: Module

Goal: Examine Module in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 04: Dependencies

Goal: Examine Dependencies in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 05: Workspaces

Goal: Examine Workspaces in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 06: Import

Goal: Examine Import in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 07: Refactoring und Testing

Goal: Examine Refactoring und Testing in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 08: State

Goal: Examine State in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 09: Backends

Goal: Examine Backends in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 10: Module

Goal: Examine Module in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 11: Dependencies

Goal: Examine Dependencies in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 12: Workspaces

Goal: Examine Workspaces in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 13: Import

Goal: Examine Import in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 14: Refactoring und Testing

Goal: Examine Refactoring und Testing in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 15: State

Goal: Examine State in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 16: Backends

Goal: Examine Backends in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 17: Module

Goal: Examine Module in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 18: Dependencies

Goal: Examine Dependencies in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 19: Workspaces

Goal: Examine Workspaces in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 20: Import

Goal: Examine Import in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 21: Refactoring und Testing

Goal: Examine Refactoring und Testing in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 22: State

Goal: Examine State in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 23: Backends

Goal: Examine Backends in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

Task 24: Module

Goal: Examine Module in an isolated OpenTofu lab and document the effect.

  1. Use an example in examples/ or create a local HCL lab.
  2. Record root module, provider requirements, backend model and expected state impact.
  3. Check HCL structure, variables, outputs and module boundaries.
  4. Describe how tofu plan would represent the change and which review questions appear.
  5. Justify the matching revert, state, import, restore or secret rotation path.

Success criterion: Another person can see which desired state is described and which state change would follow.

02 / 06

Review Checklist for Intermediate Exercises

  • 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.
03 / 06

Practice Appendix: Intermediate Exercises

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

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

A002. Backends

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

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

A004. Dependencies

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

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

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

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

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

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

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

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

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

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

A048. Backends

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

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

A050. Dependencies

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

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

  • Task: assess plan diff and explicitly relate the observation to Import.
  • 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. Refactoring und Testing

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

A071. Backends

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

A073. Dependencies

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

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

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

  • Task: assess plan diff and explicitly relate the observation to Refactoring und Testing.
  • 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. 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.

A078. Configuration

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

A079. Root Module

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

A080. Provider

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

A081. Resource

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

A082. Data Source

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

A083. Variable

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

A084. Output

  • Task: state a team rule 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.
04 / 06

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/
05 / 06

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.
06 / 06

TOF · Orthevs Academy

31 modules as one continuous learning path.

The sequence remains unchanged: from the lab skeleton through technical foundations and operating models to final troubleshooting. The technical directory names are deliberately preserved.

Practice modules

Orthevs as an app

Install Orthevs

The Orthevs web app can be installed on supported mobile devices and desktop browsers.

iPhone and iPad

Open Orthevs in Safari. Tap Share, then Add to Home Screen. Enable Open as Web App if offered, then tap Add.

Android

For the web app, open the browser menu and choose Install app or Add to Home screen. Confirm the installation.

Desktop browser

Open the browser menu or the install icon in the address bar, then choose Install app or Add to Dock.

Web app installation depends on your browser. If no install prompt appears, follow the browser steps shown above.