HashiCorp Terraform Associate (004) Question 13
Single answer1b Describe the advantages of IaC patternsA platform team manages separate development, staging, and production environments in AWS. Today, engineers create and update these environments manually in the AWS console, which has led to configuration drift, inconsistent network settings, and slow onboarding for new application teams. The team decides to standardize on Terraform and use reusable modules and version-controlled configuration files for each environment. Which advantage of this Infrastructure as Code (IaC) pattern best addresses the team's current problems?
- A
It allows teams to define infrastructure declaratively, reuse proven patterns through modules, and review changes in version control before applying them.
- B
It removes the need to run plan or review changes because Terraform modules automatically prevent all misconfigurations.
- C
It ensures every environment is identical by storing Terraform state locally on each engineer's workstation.
- D
It lets teams avoid learning cloud provider concepts because Terraform abstracts all provider-specific behavior.
Show answer and explanation
Correct answer: A
Explanation
The best answer is the option describing declarative configuration, reusable modules, and version control. These are major advantages of IaC patterns and directly address the scenario's pain points: manual provisioning, drift, inconsistency, and slow onboarding. In Terraform, reusable modules allow teams to apply the same tested infrastructure pattern across multiple environments while varying inputs as needed. Version-controlled configuration enables collaboration, code review, auditability, and rollback to previous definitions. HashiCorp documentation and Terraform best practices emphasize using configuration files as the source of truth, reviewing changes with terraform plan, and organizing reusable infrastructure with modules. Together, these patterns improve consistency, repeatability, and operational safety compared with manual console changes.
- A. Correct.
Correct. This is a core advantage of IaC patterns in Terraform. Declarative configuration makes desired state explicit, modules promote reuse and consistency across environments, and storing configuration in version control supports peer review, change history, and safer collaboration. These practices directly reduce manual errors, configuration drift, and environment inconsistency.
- B. Incorrect.
Incorrect. Terraform modules help standardize infrastructure, but they do not eliminate the need for planning, review, testing, or validation. Terraform's workflow is built around reviewing proposed changes with
terraform planbefore applying them. Modules can still be misused or contain errors if not reviewed properly. - C. Incorrect.
Incorrect. Local state on each engineer's machine does not ensure identical environments and often creates collaboration and consistency problems. Shared remote state is the recommended pattern for team workflows because it improves collaboration, locking, and visibility. Environment consistency comes from reusable code and controlled changes, not from local state files.
- D. Incorrect.
Incorrect. Terraform provides a consistent workflow across providers, but teams still need to understand provider-specific resources, limits, and behavior. Terraform does not remove the need for cloud knowledge; it helps codify and manage that knowledge more consistently.