Practise the standard verbs for managing shared terraform remote state.
0 / 5 completed
1 / 5
Fill in: 'We ___ remote state in an S3 backend so every engineer applies against the same shared source of truth.'
We 'store state' — the standard, simple collocation for persisting terraform state in a backend. The other options are less idiomatic here.
2 / 5
Fill in: 'Two engineers applying at the same time without locking can ___ the remote state file corrupted.'
We say concurrent applies will 'leave' state corrupted — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ state access with a DynamoDB lock table so two applies can never run against the same state simultaneously.'
We 'protect access' — the standard, established collocation for guarding a shared resource. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ a remote state output from one workspace as a data source in another rather than duplicating values.'
We 'reference an output' — the standard, established terraform collocation for consuming a value across state files. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ state file versions in the backend so an accidental bad apply can always be rolled back to the prior copy.'
We 'retain versions' — the standard, established collocation for keeping historical copies of a file. The other options aren't the recognised term here.