TF-004 Understand IaC concepts Practice Question
A platform team is standardizing how infrastructure is provisioned across three cloud providers using Terraform. Leadership wants to reduce the risk of undocumented manual changes and ensure that every environment can be recreated identically on demand. Which two characteristics of infrastructure as code directly support these goals? (Choose two.)
⚠ Common exam trap
The trap here is assuming Terraform continuously monitors and auto-reverts manual changes, when it only detects drift during a plan or refresh.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A single Terraform configuration can describe resources across multiple providers without maintaining separate tooling for each cloud.
Version-controlled declarative configuration provides auditable, repeatable provisioning, and Terraform's multi-provider capability lets one workflow span AWS, Azure, and Google Cloud. Together these reduce undocumented manual changes and allow identical environment recreation. The remaining choices describe either manual console workflows, continuous auto-remediation that Terraform does not perform, or an incorrect claim about state persistence.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A single Terraform configuration can describe resources across multiple providers without maintaining separate tooling for each cloud.
Why this is correct
Terraform's provider model lets one configuration declare resources for AWS, Azure, and Google Cloud simultaneously, using provider blocks and a shared workflow. This directly supports standardizing provisioning across three clouds with one tool and one process. It also keeps the definition in code so environments can be recreated identically, satisfying the stated goals.
- ✗
Infrastructure can be provisioned through the cloud provider's web console using the same templates that Terraform applies.
Why it's wrong here
Terraform does not apply its configuration through the provider web console; it calls provider APIs. Console changes are exactly the manual, undocumented modifications the team wants to eliminate. While a console can create resources, it does not consume Terraform configuration files, so it cannot deliver the auditability or reproducibility the scenario requires.
- ✓
Infrastructure definitions are stored as versioned text files that can be reviewed and audited like application code.
Why this is correct
Storing infrastructure as declarative, version-controlled text lets teams review changes through pull requests and audit history, which directly reduces undocumented manual drift. Because the same files can be applied repeatedly, environments can be recreated identically on demand. This is a core IaC characteristic and matches the leadership goal of consistent, reproducible provisioning.
- ✗
Terraform automatically detects and reverts any manual change made outside of Terraform within seconds of it occurring.
Why it's wrong here
Terraform does not run continuously or watch provider APIs for out-of-band changes. It only detects drift when a plan or refresh is executed, and even then it does not revert anything until an apply is run with approval. Claiming automatic, near-instant reversion overstates the tool's behavior and would not satisfy the requirement as described.
- ✗
Infrastructure state is stored only in memory during an apply, so no persistent artifacts remain after provisioning completes.
Why it's wrong here
Terraform persists state, by default in a local terraform.tfstate file or in a configured remote backend. State is essential for mapping configuration to real resources and for planning future changes. An in-memory-only model would prevent collaboration and drift detection. This statement is factually incorrect and does not describe an IaC benefit relevant to the scenario.
Go deeper
Related to this question
About these practice questions
This TF-004 question is part of Courseiva's 434-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official HashiCorp exam blueprint
This TF-004 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the TF-004 exam.