HashiCorp Terraform Associate (004) Question 7
Single answer1a Explain what IaC isA company has been creating cloud infrastructure manually through a provider's web console. After several production incidents, the operations team finds that environments are inconsistent, changes are hard to review, and rebuilding a failed environment takes too long. The team decides to adopt Terraform. Which outcome best demonstrates the core value of Infrastructure as Code (IaC) in this scenario?
- A
Infrastructure definitions are stored as version-controlled configuration files so teams can review, reuse, and consistently provision environments.
- B
Terraform automatically prevents all configuration drift, even when engineers continue making manual changes in the cloud console.
- C
Infrastructure is created faster because Terraform replaces the need to understand provider resources or desired state modeling.
- D
Terraform converts existing manually created infrastructure into managed code without any import or refactoring work.
Show answer and explanation
Correct answer: A
Explanation
Infrastructure as Code (IaC) means defining and managing infrastructure using machine-readable configuration files rather than manual processes. In this scenario, the main problem is inconsistency, lack of reviewability, and slow recovery. Terraform addresses this by allowing infrastructure definitions to be written as code, stored in version control, peer reviewed, reused across environments, and applied consistently. This is the core operational benefit of IaC. HashiCorp Terraform documentation emphasizes declarative configuration, execution plans, and repeatable provisioning as key concepts. While Terraform can help identify differences between desired and actual infrastructure, it does not guarantee prevention of drift caused by out-of-band manual changes, and it does not automatically convert existing infrastructure into code without import and configuration work. Best practice is to keep infrastructure changes in code, use version control, and treat infrastructure updates with the same review discipline as application changes.
- A. Correct.
Correct. This describes the central idea of IaC: infrastructure is defined in machine-readable files that can be versioned, reviewed, reused, and applied repeatedly to create consistent environments. In Terraform, these declarative configuration files allow teams to manage infrastructure similarly to application code, improving repeatability and collaboration.
- B. Incorrect.
Incorrect. IaC helps detect and reduce drift, but Terraform does not automatically prevent all drift if people keep changing resources manually outside the workflow. Manual changes can still cause the real infrastructure to differ from the configuration, and Terraform can only identify and reconcile that during plan/apply operations if the resources are managed correctly.
- C. Incorrect.
Incorrect. Terraform can improve speed and consistency, but it does not remove the need to understand cloud resources or how to model desired infrastructure state. A common misconception is that IaC tools eliminate infrastructure knowledge requirements; in practice, they encode that knowledge into reusable configuration.
- D. Incorrect.
Incorrect. Terraform can manage existing infrastructure, but typically that requires importing resources into state and ensuring the configuration matches the real infrastructure. IaC is not an automatic conversion process for unmanaged manual environments.