TF-004 Understand Terraform basics 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.

• ✓

  A new AMI was released after the apply, causing the data source to return a different AMI ID.

  Why this is correct

  When an `aws_ami` data source is configured with `most_recent = true`, Terraform dynamically queries AWS for the latest matching AMI during each `terraform plan` execution. If a new AMI is released by AWS between an `apply` and a subsequent `plan`, the data source will resolve to a different AMI ID. This change in the computed AMI ID, which is typically used by an `aws_instance` resource, will be detected by Terraform as a drift, necessitating the replacement of the existing EC2 instance to use the newly identified AMI.

• ✗

  The developer did not run terraform init before the second plan.

  Why it's wrong here

  Running `terraform init` primarily initializes the working directory by downloading necessary provider plugins and modules, and setting up backend configuration. While crucial for initial setup or when provider versions or modules change, failing to run `init` before a subsequent `plan` on an already initialized configuration would typically result in an error indicating missing providers or an uninitialized backend. It does not alter the values retrieved by data sources or cause configuration drift leading to resource replacement.

• ✗

  The instance type was changed in the configuration between apply and plan.

  Why it's wrong here

  If the `instance_type` attribute within the `aws_instance` resource block was explicitly modified in the Terraform configuration file between `apply` and `plan`, Terraform would indeed detect this as a change requiring an update or replacement of the EC2 instance. However, the problem statement implies no explicit configuration changes were made by the developer. The scenario describes an unexpected replacement *without* a direct modification to the `.tf` files, making this option inconsistent with the premise.

• ✗

  The Terraform state file was corrupted during the apply.

  Why it's wrong here

  The Terraform state file (`terraform.tfstate`) records the real-world infrastructure managed by Terraform, mapping configuration to actual resources. If the state file were corrupted, `terraform plan` would likely fail with parsing errors, inconsistencies, or an inability to match resources, rather than successfully generating a plan that proposes a clean replacement of an existing resource due to a perceived change. State corruption typically manifests as critical errors preventing any successful plan or apply operation.

Go deeper

Related to this question