Wiki workshop · Αγγλικά

OpenTofu Exercises: Advanced Security (EN)

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

Γλώσσα περιεχομένου · ΑγγλικάΜέγεθος · 72.9 KBexercises/04-advanced-security-exercises-opentofu-EN.md

Παραδείγματα workshop σε ZIP

Πρόοδος μάθησης στη web app

Σημειώστε κεφάλαια ως αναγνωσμένα, δείτε την πρόοδο ανάγνωσης και ολοκληρώστε πρακτικές ενότητες αφού ενεργοποιήσετε την προαιρετική web app. Η πρόοδος του workshop υπολογίζεται από τα κεφάλαια όλων των σελίδων τεκμηρίωσης. Οι επιλογές μένουν σε αυτή τη συσκευή· δεν υπάρχει λογαριασμός ή συγχρονισμός με server. Δεν απαιτείται εγκατάσταση. Η ανάκληση στις Ρυθμίσεις απορρήτου διαγράφει την πρόοδο.

Πρόοδος ανάγνωσης0%

0%

0 / 6 κεφάλαια που διαβάστηκαν

Δεν υπάρχει ακόμη ελληνική έκδοση αυτού του εγγράφου. Το περιεχόμενο εμφανίζεται στα αγγλικά.

Άλλη γλωσσική έκδοσηΓερμανικά ↗Ελληνικά ↗

OpenTofu Exercises: Advanced Security (EN)

These exercises belong to the workshop level Advanced Security. 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.

Required Tasks

Task 01: State-Security

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Secrets

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Provider-Pinning

Goal: Examine Provider-Pinning in an isolated OpenTofu lab and document the effect.

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Supply Chain

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Least Privilege

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Incident Response

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: State-Security

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Secrets

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Provider-Pinning

Goal: Examine Provider-Pinning in an isolated OpenTofu lab and document the effect.

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Supply Chain

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Least Privilege

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Incident Response

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: State-Security

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Secrets

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Provider-Pinning

Goal: Examine Provider-Pinning in an isolated OpenTofu lab and document the effect.

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Supply Chain

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Least Privilege

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Incident Response

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: State-Security

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Secrets

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Provider-Pinning

Goal: Examine Provider-Pinning in an isolated OpenTofu lab and document the effect.

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Supply Chain

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Least Privilege

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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: Incident Response

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

Use an example in examples/ or create a local HCL lab.
Record root module, provider requirements, backend model and expected state impact.
Check HCL structure, variables, outputs and module boundaries.
Describe how tofu plan would represent the change and which review questions appear.
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.

Practice Appendix: Advanced Security 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-Security

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

A002. Secrets

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

A003. Provider-Pinning

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

Task: assess plan diff and explicitly relate the observation to Supply Chain.
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. Least Privilege

Task: describe backend and locking model and explicitly relate the observation to Least Privilege.
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. Incident Response

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

A023. State-Security

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

A024. Secrets

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

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

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

Task: explain state impact and explicitly relate the observation to Least Privilege.
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. Incident Response

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

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

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

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

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

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

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

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

A037. Local Value

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

A038. State

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

A039. Backend

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

A040. Plan

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

A041. Apply

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

A042. Module

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

A043. Meta-Argument

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

A044. TACOS

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

A045. State-Security

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

A046. Secrets

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

Task: write down rollback or recovery path and explicitly relate the observation to Provider-Pinning.
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. Supply Chain

Task: state a team rule and explicitly relate the observation to Supply Chain.
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. Least Privilege

Task: document configuration and desired state and explicitly relate the observation to Least Privilege.
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. Incident Response

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

A051. OpenTofu

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

A052. Configuration

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

A053. Root Module

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

A054. Provider

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

A055. Resource

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

A056. Data Source

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

A057. Variable

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

A058. Output

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

A059. Local Value

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

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

A061. Backend

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

A062. Plan

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

A063. Apply

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

A064. Module

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

A065. Meta-Argument

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

A066. TACOS

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

A067. State-Security

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

A068. Secrets

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

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

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

Task: write down rollback or recovery path and explicitly relate the observation to Least Privilege.
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. Incident Response

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

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

A074. Configuration

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

A075. Root Module

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

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

A077. Resource

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

A078. Data Source

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

A079. Variable

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

A080. Output

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

A081. Local Value

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

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

A083. Backend

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

A084. Plan

Task: state a team rule 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.

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.

TOF · Orthevs Academy

31 modules ως ενιαία διαδρομή μάθησης.

Η σειρά παραμένει αμετάβλητη: από τη βασική δομή του lab μέσω τεχνικών θεμελίων και λειτουργικών μοντέλων έως το τελικό troubleshooting. Τα τεχνικά ονόματα καταλόγων διατηρούνται σκόπιμα.

Πρακτικά modules