After performing your first terraform apply, changing the backend configuration to a different backend is:

After performing your first terraform apply, changing the backend configuration to a different backend is:

• A. Mandatory
• B. Optional
• C. Impossible
• D. Discouraged

Answer: (B)

Storing state in a backend and reinitializing to move that state is a common Terraform workflow. When you change the backend configuration after you’ve done an initial apply, Terraform can reinitialize the project and migrate the existing state to the new backend. This migration capability is optional—you can choose to migrate the state now so future plans and applies use the new backend, or you can skip the migration and leave the existing state in its current backend for the time being. Terraform’s init process will typically prompt you to migrate when it detects a backend change, giving you the control to move the state only if you want to. If you decide to migrate, the state is copied to the new backend; if you don’t, you’ll keep using the old backend until you opt to migrate later.

Storing state in a backend and reinitializing to move that state is a common Terraform workflow. When you change the backend configuration after you’ve done an initial apply, Terraform can reinitialize the project and migrate the existing state to the new backend. This migration capability is optional—you can choose to migrate the state now so future plans and applies use the new backend, or you can skip the migration and leave the existing state in its current backend for the time being. Terraform’s init process will typically prompt you to migrate when it detects a backend change, giving you the control to move the state only if you want to. If you decide to migrate, the state is copied to the new backend; if you don’t, you’ll keep using the old backend until you opt to migrate later.