Collocations: Infrastructure Provisioning Language
Practice the key verb+noun collocations used when provisioning, configuring, and tearing down cloud infrastructure in English.
0 / 5 completed
1 / 5
Fill in: 'The Terraform plan will ___ three new EC2 instances in the eu-west-1 region.'
We 'provision resources' — 'provision' is the infrastructure-standard collocation for allocating and configuring cloud resources. 'Create' is generic; 'deploy' implies application deployment; 'build' refers to compilation, not infrastructure allocation.
2 / 5
Fill in: 'We can ___ a staging instance ___ in minutes using our Terraform modules.'
We 'spin up an instance' — 'spin up' is the DevOps collocation for rapidly starting a new cloud instance. 'Start up' is generic; 'bring online' implies restoring something that was down; 'launch online' is not a standard phrase.
3 / 5
Fill in: 'After the load test, we will ___ the temporary infrastructure to avoid unnecessary costs.'
We 'tear down infrastructure' — 'tear down' is the infrastructure-as-code collocation for removing all resources in an environment. 'Destroy' is the Terraform command name but 'tear down' is the conversational collocation; 'remove' and 'delete' are generic.
4 / 5
Fill in: 'Run `terraform apply` to ___ the latest configuration to the production environment.'
We 'apply a configuration' — 'apply' is both the Terraform command and the correct collocation for making a declared configuration take effect. 'Push' is used for code; 'deploy' suits applications; 'implement' is strategic, not operational.
5 / 5
Fill in: 'Unmanaged manual changes cause the live environment to ___ from its desired state.'
We say infrastructure 'drifts from desired state' — 'configuration drift' is the standard IaC collocation for uncontrolled changes that separate actual from declared state. 'Deviate' is more formal; 'differ' is static comparison; 'diverge' is used for branching paths, not configuration.