Practise the standard verbs for reviewing terraform plans safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ every terraform plan in CI so a destructive change never applies without a human reading it first.'
We 'review a plan' — the standard, established infrastructure-as-code collocation for reading proposed changes before apply. The other options aren't the recognised term here.
2 / 5
Fill in: 'A renamed resource without a moved block can ___ terraform into destroying and recreating it unnecessarily.'
We say a missing moved block will 'push' terraform into a destructive plan — the standard collocation for the resulting behaviour. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the plan output for unexpected deletions before anyone types "yes" at the apply prompt.'
We 'scan' output — the standard collocation for quickly checking a result for anomalies. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a plan artifact from CI so the exact reviewed plan is what actually gets applied.'
We 'save' an artifact — the standard, simple collocation for persisting a build output for later use. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ state locking during a plan so two engineers never run terraform against the same state at once.'
We 'enforce locking' — the standard, established collocation for requiring a safety mechanism. The other options aren't the recognised term here.