HashiCorp Terraform Associate (004) Question 6
Single answer1a Explain what IaC isA company has been creating cloud infrastructure manually through the provider's web console. After several production incidents, the platform team decides to adopt Terraform so that development, staging, and production environments can be created consistently and reviewed before changes are made. Which outcome best demonstrates the core value of Infrastructure as Code (IaC) in this scenario?
- A
Infrastructure definitions are stored in version-controlled files, allowing the team to review, reuse, and apply the same desired configuration across environments.
- B
Terraform replaces the cloud provider's APIs, so infrastructure changes no longer depend on the provider's platform.
- C
IaC guarantees that infrastructure provisioning will succeed without any manual decisions or approvals.
- D
Infrastructure is configured only after resources are manually created, which reduces the need for planning changes in advance.
Show answer and explanation
Correct answer: A
Explanation
Infrastructure as Code (IaC) means defining and managing infrastructure through machine-readable configuration files rather than manual point-and-click actions. In Terraform, this is typically done with declarative configuration that expresses the desired end state. The practical benefits include consistency across environments, repeatability, version control, peer review, and the ability to preview changes with a plan before applying them. This is why option 1 best matches the scenario. HashiCorp documentation describes Terraform as infrastructure as code that allows you to define both cloud and on-prem resources in configuration files, then provision and manage them in a consistent workflow. These practices also align with common DevOps and platform engineering best practices for reducing configuration drift and improving auditability.
- A. Correct.
Correct. This describes the central idea of IaC: infrastructure is defined in machine-readable configuration files and treated similarly to application code. With Terraform, those files can be version controlled, peer reviewed, reused across environments, and applied consistently. This directly addresses the team's goals of consistency, repeatability, and change visibility.
- B. Incorrect.
Incorrect. Terraform does not replace provider APIs. It uses provider plugins to interact with cloud and other service APIs. A common misconception is that IaC bypasses the underlying platform, but Terraform depends on those APIs to create, update, and destroy infrastructure.
- C. Incorrect.
Incorrect. IaC improves automation and repeatability, but it does not guarantee successful provisioning in every case. Failures can still occur due to invalid configuration, permissions issues, quota limits, unavailable services, or policy constraints. Manual approvals may still be part of the team's workflow.
- D. Incorrect.
Incorrect. This is closer to manual infrastructure management than IaC. In IaC, the desired infrastructure is declared before creation or modification so changes can be planned, reviewed, and applied in a controlled way. Creating resources manually first undermines consistency and traceability.