TF-004 Understand IaC concepts Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Storing state files remotely and locking them

  Why this is correct

  Storing Terraform state files remotely, typically in a backend like S3, Azure Blob Storage, or HashiCorp Consul, centralizes the authoritative record of managed infrastructure. This remote storage, combined with state locking mechanisms provided by the backend, prevents multiple users or automated processes from concurrently modifying the state file. This ensures that only one operation can write to the state at a time, preventing race conditions, state corruption, and configuration drift caused by uncoordinated changes.

• ✓

  Implementing CI/CD pipelines with automated testing

  Why this is correct

  Integrating Terraform into CI/CD pipelines ensures that infrastructure changes are systematically reviewed, validated, and applied through a consistent, repeatable process. Automated testing within these pipelines, including `terraform validate`, `terraform plan` checks, and potentially integration tests, catches errors early and verifies that proposed changes align with desired configurations. This automation minimizes human error, enforces best practices, and guarantees that infrastructure deployments are consistent across environments.

• ✓

  Regularly running terraform plan and apply

  Why this is correct

  Regularly executing `terraform plan` allows teams to preview proposed infrastructure changes and identify any drift between the actual infrastructure and the desired state defined in configuration files. Following up with `terraform apply` then reconciles these differences, ensuring that the infrastructure consistently matches the declared configuration. This proactive approach helps detect and correct unauthorized or manual changes, thereby maintaining consistency and preventing significant divergence over time.

• ✗

  Using manual changes to fix minor issues

  Why it's wrong here

  Directly making manual changes to infrastructure resources outside of Terraform, even for seemingly minor issues, immediately introduces configuration drift. These changes are not reflected in the Terraform state file or configuration, leading to discrepancies between the desired state and the actual infrastructure. Subsequent `terraform apply` operations might then attempt to revert these manual fixes or fail due to unexpected resource states, undermining consistency and making infrastructure management unpredictable.

• ✗

  Allowing multiple team members to run apply simultaneously

  Why it's wrong here

  Permitting multiple team members to execute `terraform apply` commands concurrently without proper state locking mechanisms creates a high risk of state file corruption and conflicting infrastructure changes. Without a lock, simultaneous operations could attempt to write to the same state file, leading to an inconsistent or corrupted record of the infrastructure. This can result in resources being incorrectly provisioned, modified, or destroyed, severely compromising consistency and operational stability.

Go deeper

Related to this question