Budget planning and financial communication require precise professional collocations. This quiz covers the standard phrases for submitting budgets, justifying expenditure, allocating headcount, and optimising spend.
0 / 5 completed
1 / 5
Fill in: 'Each VP of Engineering must ___ a detailed budget request to Finance by the end of September.'
We 'submit a budget' — 'submit' is the formal collocation for delivering a budget proposal to an approving authority within a defined process. 'Send a budget' is informal; 'present a budget' focuses on the verbal delivery; 'file a budget' is more common in legal and administrative contexts.
2 / 5
Fill in: 'The team had to ___ the costs for migrating to a managed Kubernetes service in the business case.'
We 'justify costs' — 'justify' is the business standard for demonstrating that expenditure is necessary and proportionate to the expected benefit. 'Explain costs' is too neutral and does not imply the ROI argument required in budget reviews; 'defend' implies the costs are already under attack; 'support costs' is not a natural collocation.
3 / 5
Fill in: 'HR confirmed they have approval to ___ two additional senior engineers to the platform team in Q2.'
We 'allocate headcount' — 'allocate headcount' is the budget and workforce planning standard for distributing approved personnel slots to teams. 'Hire' describes the recruitment process; 'add' is generic; 'assign headcount' is close but 'allocate' better captures the organisational planning and budgetary approval implied.
4 / 5
Fill in: 'Finance requires all engineering teams to ___ their cloud spend against the approved budget monthly.'
We 'track spend' — 'track spend' is the financial management standard for continuously comparing actual expenditure against planned amounts. 'Monitor spend' is close but emphasises oversight rather than comparison; 'report spend' focuses on the communication output; 'measure spend' implies a one-time calculation.
5 / 5
Fill in: 'The platform team is under pressure to ___ cloud spend by 20% without impacting service reliability.'
We 'optimise cloud spend' — 'optimise' is the cloud FinOps standard for reducing cost while maintaining or improving efficiency, implying architectural changes rather than simple cuts. 'Reduce cloud spend' is accurate; 'cut cloud spend' implies blunt reductions; 'lower cloud spend' is informal. 'Optimise' is preferred because it implies intelligent trade-offs rather than sacrifice.