Practice the key verb+noun collocations used in FinOps and cloud cost optimization discussions in English.
0 / 5 completed
1 / 5
Fill in: 'The FinOps team identified several ways to ___ cloud spend by 30% this quarter.'
We 'reduce cloud spend' — 'reduce' is the professional FinOps collocation for systematically bringing down cloud costs. 'Cut' implies aggressive, one-time reduction; 'lower' is informal; 'decrease' is more academic and less action-oriented.
2 / 5
Fill in: 'We should ___ our database instances, as they are currently over-provisioned for actual load.'
We 'right-size instances' — 'right-size' is the cloud cost management collocation for adjusting resources to match actual demand. 'Resize' is generic; 'downsize' implies reduction only; 'scale down' focuses on reducing capacity in response to load, not cost optimisation.
3 / 5
Fill in: 'The cloud cost report helped us ___ idle resources that were running 24/7 without traffic.'
We 'identify waste' — 'identify' is the FinOps collocation for formally recognising and naming unnecessary spend. 'Find waste' is informal; 'spot waste' implies accidental discovery; 'detect waste' is more suited to monitoring tools.
4 / 5
Fill in: 'We need to ___ all resources with project and team labels so costs can be attributed correctly.'
We 'tag resources' — 'tag' is the AWS/Azure/GCP-standard collocation for attaching key-value metadata to cloud resources for cost allocation. 'Label' is used specifically in GCP, not as a universal term; 'mark' is informal; 'annotate' is used for code and documents.
5 / 5
Fill in: 'We are working to ___ unit economics so each customer transaction becomes more profitable.'
We 'optimize unit economics' — 'optimize' is the FinOps and product collocation for improving the cost and revenue structure per unit. 'Improve unit economics' is also correct but 'optimize' carries the specific sense of making trade-offs efficiently; 'fix' implies something is broken; 'enhance' is less business-focused.