5 collocation exercises on managing and optimising cloud spend.
0 / 5 completed
1 / 5
To plan cloud budgets, you ___ spend.
You forecast spend — projecting future cloud costs based on usage trends and planned growth. Forecast collocates with spend, cost and demand. Guess off, predict up and reckon out are not idiomatic. Forecasting spend lets finance and engineering set realistic budgets and spot when projected costs will exceed plan, so action can be taken before the bill surprises anyone.
2 / 5
For cost attribution, you ___ resources.
You tag resources — attaching metadata labels (team, project, environment) so costs can be attributed and reported. Tag is the standard cloud collocation (tagging strategy, cost allocation tags). Label off, mark up and stamp out are not idiomatic. Consistent tagging is the foundation of cost management; without it, you cannot tell which team or product is driving spend on a shared cloud account.
3 / 5
For steady workloads, you ___ instances to save money.
You reserve instances — committing to a one- or three-year term in exchange for a large discount over on-demand pricing. Reserve collocates with instances and capacity (reserved instances, RIs). Book off, hold up and claim out are not the standard term. Reserving instances suits predictable, always-on workloads, while spiky or experimental workloads are better left on-demand or on spot pricing.
4 / 5
To match capacity to actual need, you ___ instances.
You right-size instances — adjusting them to match real usage, downgrading over-provisioned resources. Right-size (or rightsizing) is the standard cost-optimisation term. Fit off, trim up and shrink out are not idiomatic. Right-sizing is one of the quickest wins in cloud cost control: many resources run far larger than needed, and downsizing them cuts the bill with no performance impact.
5 / 5
When costs spike unexpectedly, the system should ___ an anomaly.
The system flags an anomaly — raising an alert when spend deviates sharply from normal patterns. Flag collocates with anomaly, issue and risk. Wave off, mark up and signal out are not the collocation. Anomaly detection catches runaway costs early — a misconfigured job or forgotten resource — before a small mistake becomes a large, unexpected charge at month-end.