Practise the standard verbs for managing Terraform state locks safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a lock on the state file so two engineers can't apply changes at the same time.'
We 'acquire a lock' — the standard, established Terraform collocation for claiming exclusive access. The other options aren't the recognised term here.
2 / 5
Fill in: 'A crashed apply that never ___ its lock can block every subsequent run indefinitely.'
We say a run 'releases' its lock — the standard collocation for giving up exclusive access. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the remote backend so state locking works consistently across the whole team.'
We 'configure' a backend — the standard collocation for setting up shared infrastructure state. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a stuck lock manually only after confirming no apply is genuinely still running.'
We 'force-unlock' — the standard, established Terraform command name and collocation for the manual override. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ concurrent applies in CI so pipeline runs never race for the same lock.'
We 'serialise' applies — the standard collocation for forcing them through one path. The other options aren't idiomatic here.