Which strategy is described by Savings pool?

• A. All savings are allocated to a central savings pool managed by finance and distributed to the business.
• B. Savings are ignored and absorbed by the FinOps team.
• C. Savings are kept by the team that achieved them and not redistributed.
• D. Savings are used to extend the reservation term automatically.

Answer: (A)

The key idea is to centralize the benefits of cost savings. When optimization work—like rightsizing, shutting underutilized resources, or leveraging reservations—produces real dollar savings, those gains are funneled into a single Savings pool. Finance or a dedicated FinOps function then governs and redistributes those funds back to the business, funding ongoing optimization, other initiatives, or budget to teams as appropriate. This centralized approach ensures transparency, prevents windfalls from staying with one team, and strengthens collaboration across the organization.

That’s why the described strategy is best: all savings go into a central pool managed by finance and are distributed to the business. It captures the governance and broad benefit that organizations aim for in FinOps.

Savings being ignored removes accountability and the opportunity to reinvest; savings staying with the team undermines governance and shared benefit; using savings to extend a reservation term automatically is a specific operational choice, not the defining behavior of a centralized savings pool.