Which command migrates your current state file to a new S3 remote backend?

Which command migrates your current state file to a new S3 remote backend?

• A. terraform init
• B. terraform apply
• C. terraform refresh
• D. terraform push

Answer: (A)

Switching where Terraform stores its state (for example, to a new S3 remote backend) requires reinitializing Terraform so it can copy the existing state to the new location. Running Terraform init performs this migration: it reads the backend configuration, connects to S3, and moves your current state from the local file to the S3 bucket. You’ll typically be prompted to approve the migration, and you can force it with the -migrate-state flag if needed. After this, Terraform will manage future state in S3. Other commands don’t migrate the state to a new backend: applying changes, refreshing state from real resources, or pushing state are not used for backend migrations.

Switching where Terraform stores its state (for example, to a new S3 remote backend) requires reinitializing Terraform so it can copy the existing state to the new location. Running Terraform init performs this migration: it reads the backend configuration, connects to S3, and moves your current state from the local file to the S3 bucket. You’ll typically be prompted to approve the migration, and you can force it with the -migrate-state flag if needed. After this, Terraform will manage future state in S3. Other commands don’t migrate the state to a new backend: applying changes, refreshing state from real resources, or pushing state are not used for backend migrations.