FinOps Certified Practitioner flashcards
FinOps Certified Practitioner · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- FinOps definition
- FinOps is an operating model and cultural practice that brings financial accountability to variable technology spend, enabling teams to make data-driven trade-offs between cost, quality, and speed.
- FinOps principle: collaboration
- Teams across finance, technology, and business must collaborate, because cost decisions and usage decisions are made in different roles and require shared context to be effective.
- Business value principle
- Technology decisions should be driven by business value, not by lowest cost alone; FinOps evaluates cost against quality, speed, revenue impact, and risk.
- Ownership principle
- Everyone who consumes or approves technology resources takes ownership for usage and cost, rather than delegating all accountability to a central FinOps team.
- FinOps lifecycle phases
- The continuous FinOps cycle is Inform, Optimize, and Operate; Inform provides visibility, Optimize improves cost, and Operate sustains accountability and automation.
- Crawl Walk Run maturity
- Crawl, Walk, and Run describe increasing capability maturity, from manual and reactive processes to repeatable practices and then automated, proactive, business-aligned operations.
- Unit cost formula
- Unit cost equals total technology cost divided by a business metric, such as cost per transaction or cost per active user, enabling comparison across time and teams.
- FinOps practitioner persona
- The FinOps practitioner enables the practice by defining cost data standards, facilitating reviews, and coaching teams; the role does not solely own every spending decision.
- Engineering persona
- Engineers choose and operate technology resources, so they need granular usage and cost data to rightsize, remove waste, and make architecture trade-offs.
- Finance persona
- Finance owns budgeting, forecasting, accounting treatment, and variance analysis, and needs reconciled cost data to align technology spend with financial plans.
- Procurement persona
- Procurement manages vendor contracts, discounts, commitments, and renewals, and needs usage forecasts to negotiate terms that match expected consumption.
- Product persona
- Product owners connect technology cost to product outcomes, using unit economics and feature-level profitability to prioritize investments and pricing decisions.
- Leadership persona
- Executive leaders set risk appetite and priorities, using portfolio-level cost, forecast, and business-value views to make investment and trade-off decisions.
- Inform phase outputs
- Inform produces timely, accurate, allocated cost and usage data, plus forecasts and budgets, so teams can see what is spent and who owns it.
- Optimize phase focus
- Optimize changes consumption and prices through rightsizing, scheduling, waste removal, commitment purchases, and discount negotiations while preserving required performance.
- Operate phase focus
- Operate sustains FinOps through governance, automation, accountability reviews, and continuous improvement so savings and visibility persist over time.
- Rate optimization
- Rate optimization lowers the price paid per unit of usage through commitments, reserved capacity, negotiated discounts, and vendor terms rather than changing consumption.
- Usage optimization
- Usage optimization reduces or reshapes consumption through rightsizing, idle-resource removal, scheduling, architecture changes, and storage tiering while meeting business requirements.
- Maturity assessment rule
- Maturity is assessed per capability and scope, not as one organization-wide score, because a team may be advanced in forecasting but still crawling in allocation.
- Understand Usage and Cost
- This FinOps domain covers data ingestion, allocation, reporting, anomaly management, forecasting, and budgeting so organizations can see and explain technology spend.
- Quantify Business Value
- This domain links technology cost to business outcomes through planning, unit economics, and benchmarking, helping leaders judge whether spend creates proportionate value.
- Optimize Usage and Cost
- This domain contains capabilities that reduce cost through usage optimization, rate optimization, licensing and SaaS management, and sustainability practices.
- Manage FinOps Practice
- This domain covers practice operations, education and enablement, assessment, policy and governance, chargeback and showback, and automation to run FinOps consistently.
- Showback vs chargeback
- Showback reports costs to teams without billing them, while chargeback actually bills or transfers costs to responsible budgets; both depend on accurate allocation.
- Allocation capability
- Allocation assigns shared and direct technology costs to owners using tags, accounts, projects, or splits; it is a prerequisite for showback, chargeback, and unit economics.
- Anomaly management
- Anomaly management detects unexpected cost or usage changes using thresholds, trends, or machine learning, then alerts owners so they can investigate and remediate quickly.
- FinOps scope definition
- A FinOps scope is the boundary of technology spend being managed, such as public cloud, SaaS, data center, or licensed software, each with different cost drivers.
- Public cloud scope
- Public cloud spend is variable and usage-based, with cost drivers including compute hours, storage volume, network egress, and commitment coverage; data comes from provider billing exports.
- SaaS scope
- SaaS spend is often subscription-based, with cost drivers including seats, tiers, usage limits, and renewals; management focuses on license utilization and contract terms.
- Data center scope
- Data center or on-premises spend includes depreciation, power, cooling, space, and support contracts, so FinOps must use asset and facilities data rather than cloud bills.
- Technology category examples
- Technology categories include compute, storage, network, databases, containers, serverless, and analytics; each category has distinct optimization levers and cost metrics.
- Container allocation rule
- For containers and serverless, allocate shared cluster or platform costs to namespaces, workloads, or teams using usage metrics such as CPU, memory, requests, or execution time.