Terraform Workspace Isolation Language Collocations
Practise the standard verbs for isolating terraform workspaces safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a separate workspace per environment so a staging apply can never accidentally touch production state.'
We 'create a workspace' — the standard, established terraform collocation for provisioning an isolated state context. The other options aren't the recognised term here.
2 / 5
Fill in: 'Sharing one workspace across environments can ___ a variable meant for staging silently applied to production.'
We say a shared workspace will 'leave' a variable misapplied — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the current workspace name in the shell prompt so nobody applies against production while thinking they're in staging.'
We 'display' a name — the standard, simple collocation for showing an active context value. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ workspace-specific variable files so each environment's values never leak into another's plan.'
We 'maintain' files — the standard collocation for keeping per-environment config current. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ access to the production workspace to a small approved group rather than the whole engineering org.'
We 'restrict access' — the standard, established collocation for limiting who can act on a resource. The other options aren't the recognised term here.