When should you use the force-unlock command?

When should you use the force-unlock command?

• A. You see a status message that you cannot acquire the lock
• B. You have a high priority change
• C. Automatic unlocking failed
• D. You apply failed due to a state lock

Answer: (C)

State locking prevents concurrent writes to the Terraform state. The force-unlock command is intended for situations where the automatic unlocking doesn’t happen, leaving the lock in place. If a previous operation crashed or the lock didn’t release for some reason, you can forcibly unlock the state (using the lock ID shown in the error) and then proceed. Use this only when you’re sure no other Terraform process is actually using the state, because forcing unlock can corrupt the state if another operation is still in progress. After unlocking, run a plan to verify everything is consistent.

State locking prevents concurrent writes to the Terraform state. The force-unlock command is intended for situations where the automatic unlocking doesn’t happen, leaving the lock in place. If a previous operation crashed or the lock didn’t release for some reason, you can forcibly unlock the state (using the lock ID shown in the error) and then proceed. Use this only when you’re sure no other Terraform process is actually using the state, because forcing unlock can corrupt the state if another operation is still in progress. After unlocking, run a plan to verify everything is consistent.