Test yourself
OpenTofu
Final exam · 12 questions · answers explained as you pick
Beginner
4 questions
01OpenTofu was created because Terraform…
Incorrect — performance was not the driver; licensing was.
Correct — OpenTofu is that fork, donated to the Linux Foundation under MPL 2.0.
Incorrect — provider support was never the issue.
Incorrect — OpenTofu uses the same HCL; the language did not change.
02Relative to the terraform CLI, the tofu CLI is…
Incorrect — it deliberately mirrors terraform.
Incorrect — it ships for all major platforms.
Correct — point tofu at a Terraform project and init/plan/apply work unchanged.
Incorrect — it is a CLI like terraform.
03By default, tofu downloads providers from…
Correct — it uses the OpenTofu registry rather than registry.terraform.io — matters if you allowlist a registry host.
Incorrect — GitHub can host modules, but providers resolve via the registry.
Incorrect — the default host differs; that is a common init gotcha behind a proxy.
Incorrect — OpenTofu does not use npm.
04In a plan, the symbol that means destroy-and-recreate (potential data loss) is…
Incorrect — + is a plain create.
Incorrect — ~ is an in-place update.
Correct — the resource is destroyed then recreated — downtime and data loss for stateful resources. Read before applying.
Incorrect — # is a comment.
4 questions · explanations appear as you answer
Intermediate
4 questions
01The acceptance test that a Terraform→OpenTofu migration is sound is…
Incorrect — speed is not the signal.
Correct — a clean plan means the compatible config and state matched reality — proceed; anything else, investigate.
Incorrect — state size is irrelevant to correctness.
Incorrect — providers should resolve to the same ones; a change would be a red flag.
02What most needs an OpenTofu equivalent when leaving Terraform Cloud?
Correct — those are HashiCorp-specific; the open stack replaces them.
Incorrect — providers are identical across both.
Incorrect — the language is shared.
Incorrect — variables work the same.
03A remote backend with a lock table (e.g. S3 + DynamoDB) primarily prevents…
Incorrect — locking does not encrypt; it serializes access.
Incorrect — locking is about safety, not speed.
Correct — the lock ensures only one apply mutates state at a time.
Incorrect — unrelated to provider resolution.
04Committing .terraform.lock.hcl matters because it…
Incorrect — it holds no secrets — it pins provider versions and hashes.
Correct — so providers cannot be silently swapped under you — a supply-chain control.
Incorrect — its purpose is integrity, not speed.
Incorrect — workspaces do not depend on the lock file.
4 questions · explanations appear as you answer
Advanced
4 questions
01OpenTofu’s client-side state encryption is stronger than backend (server-side) encryption because…
Correct — server-side encryption still returns plaintext to anyone who can read the bucket via the API.
Incorrect — performance is not the point.
Incorrect — you still use a backend; the contents are just encrypted before write.
Incorrect — it protects contents, not merely counts.
02The main operational risk of enabling client-side state encryption is…
Incorrect — init speed is not the concern.
Correct — use managed KMS with backups and a rotation plan; a lost static key means lost state.
Incorrect — encryption does not affect providers.
Incorrect — locking is independent of encryption.
03Early (dynamic) variable evaluation lets OpenTofu do what Terraform forbids, such as…
Incorrect — provider count is unrelated.
Incorrect — init is still required.
Correct — Terraform resolves those before variables and rejects it; OpenTofu evaluates them earlier.
Incorrect — the language is still HCL.
04For a policy gate that sees values computed at plan time, you should run…
Incorrect — static scanners miss anything resolved at plan time (a public flag from a variable).
Correct — the plan JSON has resolved values, so the policy sees the real outcome — the authoritative gate.
Incorrect — un-gated applies to prod are the risk being removed.
Incorrect — grep cannot reason about resolved plan state.
4 questions · explanations appear as you answer