When you modify your local Terraform configuration and run terraform plan while a teammate has concurrently modified the infrastructure, the execution plan for terraform apply will be the same.

When you modify your local Terraform configuration and run terraform plan while a teammate has concurrently modified the infrastructure, the execution plan for terraform apply will be the same.

• A. True
• B. It depends
• C. False
• D. Cannot be determined

Answer: (C)

When planning and applying, Terraform bases its decisions on the current state it has. If a teammate changes the real infrastructure while you’re working, the state drifts from what you planned against. When you run apply, Terraform will refresh the state and typically recalculate a new plan to reach the desired configuration, which can yield different changes than the plan you previously saw. Unless you explicitly save a plan file (for example, with -out and then apply that plan), the apply step generates and executes a new plan, so the execution plan is not guaranteed to be the same. To lock in a specific plan, save it and apply that exact plan file.

When planning and applying, Terraform bases its decisions on the current state it has. If a teammate changes the real infrastructure while you’re working, the state drifts from what you planned against. When you run apply, Terraform will refresh the state and typically recalculate a new plan to reach the desired configuration, which can yield different changes than the plan you previously saw. Unless you explicitly save a plan file (for example, with -out and then apply that plan), the apply step generates and executes a new plan, so the execution plan is not guaranteed to be the same. To lock in a specific plan, save it and apply that exact plan file.