TF-004 Implement and maintain state 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.

• ✓

  Execute `terraform init` and confirm yes when prompted to copy existing state

  Why this is correct

  When migrating from a local state to a remote backend like S3, `terraform init` is the authoritative command. It detects the change in the `backend` configuration block within your `.tf` files. Upon execution, Terraform prompts the user to confirm the migration, offering to copy the existing local `terraform.tfstate` file to the newly configured remote backend, ensuring a seamless and consistent transition of the state management.

• ✗

  Run `terraform state push` to upload the local state

  Why it's wrong here

  The `terraform state push` command, while historically present, is now deprecated and not the correct method for migrating an entire backend. Its primary function was to upload a *local* state file to an *already configured* remote backend, not to initiate or manage the backend configuration change itself. Relying on this command for a backend migration would bypass Terraform's built-in safety mechanisms and proper backend initialization process, potentially leading to an unmanaged or inconsistent state.

• ✗

  Delete the local state file and run `terraform apply` to recreate

  Why it's wrong here

  Deleting the local `terraform.tfstate` file before running `terraform apply` is highly destructive and fundamentally misunderstands Terraform's state management. Without a state file, Terraform loses all knowledge of the infrastructure it previously provisioned. A subsequent `terraform apply` would then attempt to create *new* resources based on the configuration, leading to resource duplication, errors if resources already exist, or even the destruction and recreation of existing infrastructure, rather than a controlled migration.

• ✗

  Manually copy the state file to S3 using AWS CLI

  Why it's wrong here

  Manually copying the `terraform.tfstate` file to an S3 bucket using the AWS CLI is insufficient because it only moves the file, not the backend configuration. Terraform itself would remain unaware of this manual action and would still expect to find the state either locally or at its previously configured location. This approach fails to update Terraform's internal understanding of the backend, resulting in a 'state not found' error or the creation of a new, empty state file in S3, thereby breaking the critical link between the configuration and the actual infrastructure state.