Cheat sheet
FinOps Certified Practitioner Cheat Sheet
Challenge of Cloud
- Not published of exam
- Variable Spend Decentralized Access CapEx to OpEx Elastic Scale
What Is FinOps and Principles
- Not published of exam
- FinOps Definition Six Principles Business Value Shared Accountability
FinOps Teams and Motivation
- Not published of exam
- Core Personas Allied Personas Operating Models Culture Change
FinOps Capabilities
- Not published of exam
- Allocation Forecasting Anomaly Management Rate Optimization Workload Optimization Discount Types
FinOps Lifecycle
- Not published of exam
- Inform Phase Optimize Phase Operate Phase Maturity Model
Terminology and the Cloud Bill
- Not published of exam
- Cloud Bill Anatomy Tagging and Allocation Data in the Path Amortized Cost
Quick Facts
- Exam FOCP
- Credential FinOps Certified Practitioner
- Questions 50
- Time 60 minutes
- Pass Score 75%
- Format Unproctored online exam
- Level Foundational
- Attempts 3 in 12 months
- Validity 24 months
Cloud Cost Challenges CH
- Variable Spend Usage-based unpredictable billing
- Decentralized Access Any team can provision
- CapEx to OpEx Shift asset to expense
- Elastic Scale Scale up or down fast
- Multi-Cloud Billing Multiple provider invoices monthly
Six Principles Quick Recall PR
- Collaborate, value, own, data, central, variable cost
- Collaborate across all teams Value beats pure cost Own your own usage Data must be accessible Central team enables FinOps Exploit variable cloud pricing
FinOps Definition PR
- FinOps Maximizes tech business value
- Operating Model Not just cost cutting
- Cultural Practice Cross-team collaborative behavior
- Timely Decisions Fast data-driven choices
- Shared Accountability Engineering, finance, business together
Six FinOps Principles PR
- Collaborate Teams work together
- Business Value Value over pure savings
- Ownership Everyone owns their usage
- Accessible Data Timely and accurate access
- Central Enablement Central team enables FinOps
- Variable Cost Exploit elastic cloud pricing
Centralized vs Decentralized FinOps TE
Centralized
- Single FinOps team
- Consistent governance rules
- Slower to scale
Decentralized
- Embedded per team
- Faster local decisions
- Harder to standardize
- Consistency vs speed tradeoff
Core FinOps Personas TE
- Practitioner Drives the FinOps practice
- Engineering Builds and optimizes workloads
- Finance Owns budgets and forecasts
- Leadership Sets priorities and goals
- Product Balances features against cost
- Procurement Negotiates vendor contract terms
Allied Personas TE
- ITAM Tracks asset lifecycle
- ITFM IT financial management
- ITSM IT service management
- Security Manages risk and compliance
- Sustainability Tracks carbon footprint impact
FinOps Operating Models TE
- Centralized Single central FinOps team
- Decentralized Embedded within each team
- Hub and Spoke Central plus embedded staff
- Federated Business unit led practice
Four Capability Domain Groups CA
- Understand, then Quantify, then Optimize, then Manage
- Understand: usage and cost Quantify: business value data Optimize: usage and rate Manage: the FinOps practice
Showback vs Chargeback CA
Showback
- Reports cost only
- No real billing
- Raises team awareness
Chargeback
- Bills team budgets
- Real internal transfer
- Drives accountability
- Show cost vs bill it
Which Discount Type to Use CA
- Short unpredictable workload → On-Demand pricing
- Interruptible fault-tolerant batch job → Spot instance
- Stable steady-state compute need → Reserved Instance
- Flexible compute spend commitment → Savings Plan
- Steady GCP spend commitment → Committed Use Discount
- Need absolute lowest price → Spot instance ( Accept interruption risk )
Understand Usage and Cost CA
- Data Ingestion Collect raw billing data
- Allocation Assign cost to owners
- Reporting and Analytics Visualize spend and trends
- Anomaly Management Detect unexpected cost spikes
Discount Savings Ladder Order CA
- On-Demand costs most, Spot discounts most
- On-Demand: no discount applied RI or SP: commit discount Spot: deepest possible discount
Reserved Instance vs Savings Plan CA
Reserved Instance
- Capacity commitment
- Specific instance type
- Region or zone locked
Savings Plan
- Spend commitment
- Flexible instance family
- Broader service coverage
- Capacity commit vs spend commit
Which Capability Applies Here CA
- Cost spike suddenly appears → Anomaly Management
- Assign cost by team → Allocation
- Predict next quarter spend → Forecasting
- Measure cost per customer → Unit Economics
- Right-size an idle VM → Usage Optimization
- Bill teams for shared cost → Invoicing and Chargeback
Quantify Business Value CA
- Planning and Estimating Budget future spend forecasts
- Forecasting Predict upcoming cloud spend
- Budgeting Set team spend targets
- KPIs and Benchmarking Measure and compare efficiency
- Unit Economics Cost per business outcome
On-Demand vs Spot Instances CA
On-Demand
- No commitment required
- Highest unit price
- Never interrupted
Spot
- Steep price discount
- Can be reclaimed
- Best for fault-tolerant jobs
- Reliable vs cheap and risky
Optimize Usage and Cost CA
- Architecting Pick right region service
- Usage Optimization Rightsize or shut down idle
- Rate Optimization Lower the unit price
- Licensing and SaaS Manage software license spend
- Sustainability Reduce cloud carbon footprint
Manage the FinOps Practice CA
- Executive Strategy Alignment Tie spend to strategy
- Practice Operations Run the daily practice
- Governance and Risk Enforce spend guardrails, policy
- Education and Enablement Train stakeholders on FinOps
- Invoicing and Chargeback Bill costs back internally
- FinOps Assessment Measure organizational FinOps maturity
Discount and Commitment Types CA
- On-Demand Pay as you go
- Spot Instance Interruptible steep discount
- Reserved Instance Capacity commitment discount
- Savings Plan Flexible spend commitment
- Committed Use Discount GCP spend commitment
FinOps Lifecycle Order LI
- Inform first, then Optimize, then Operate continuously
- Inform: build visibility Optimize: take action Operate: sustain the habit
Inform vs Optimize Phase LI
Inform
- Builds spend visibility
- Allocates and reports cost
- Sets baseline data
Optimize
- Acts on findings
- Rightsizes and buys discounts
- Reduces waste
- See spend vs fix spend
Which Lifecycle Phase Applies LI
- Need cost visibility first → Inform phase ( Allocate and report )
- Found savings or waste → Optimize phase ( Buy rate discounts )
- Sustaining daily FinOps habits → Operate phase ( Govern and automate )
- Setting KPIs or benchmarks → Inform phase ( Benchmark against peers )
- Buying reserved commitments → Optimize phase ( Rate optimization action )
- Enforcing tagging policy daily → Operate phase ( Governance and automation )
Inform Phase Activities LI
- Allocation Tag and assign cost
- Reporting Build dashboards for visibility
- Budgeting Set spend expectations early
- Benchmarking Compare cost against peers
Optimize Phase Activities LI
- Rate Optimization Buy commitments for discounts
- Usage Optimization Rightsize or shut down
- Workload Optimization Re-architect for lower cost
- Waste Elimination Remove idle unused resources
Operate Phase Activities LI
- Governance Enforce ongoing spend policies
- Automation Automate continuous corrective action
- KPIs Track outcomes against targets
- Culture Sustain shared accountability habits
FinOps Maturity Model LI
- Crawl Manual basic FinOps practice
- Walk Partial process automation exists
- Run Fully automated mature practice
- Assessed per capability Maturity varies by capability
Amortized vs Net Cost TE
Amortized Cost
- Spreads commitment cost
- Smooths spend over term
- Shows true usage
Net Cost
- Actual invoiced amount
- Includes one-time charges
- Real cash impact
- Smoothed cost vs actual bill
Cloud Bill Anatomy TE
- List Price Published on-demand rate
- Effective Price Rate after all discounts
- Usage Quantity of resource consumed
- Amortized Cost Commitment cost spread evenly
- Net Cost Final actual billed amount
Tagging and Allocation TE
- Tag Cost metadata key-value label
- Label GCP and Azure tag term
- Shared Cost Split across multiple teams
- Untagged Cost Unallocated unassigned cloud spend
- Allocation Key Rule used to split cost
Data in the Path TE
- CUR AWS detailed billing export
- Raw Usage Data Unprocessed cost and usage records
- Normalization Standardize units across providers
- Data Pipeline Moves data into reporting
Common Traps
Showback vs Chargeback Confusion
- Showback only reports cost ≠ Chargeback actually bills budgets
Cost Cutting vs FinOps Goal
- FinOps maximizes business value ≠ Not simply reducing all spend
Reserved Instance vs Savings Plan
- RI locks specific instance type ≠ SP allows flexible spend commit
Practitioner vs Other Personas
- Practitioner drives the practice ≠ Other personas execute FinOps work
Inform vs Optimize Activity
- Inform only builds visibility ≠ Optimize actually takes action
Tag vs Allocation Key
- Tag is a metadata label ≠ Allocation key splits shared cost
Amortized vs Invoiced Cost
- Amortized spreads commitment cost ≠ Invoice shows actual billed amount
Last Minute
- 1. 50 questions in 60 minutes
- 2. Pass with 75% or higher
- 3. Exam is unproctored online test
- 4. Three attempts within twelve months
- 5. Credential valid for 24 months
- 6. Phases: Inform, Optimize, then Operate
- 7. FinOps maximizes value, not savings
- 8. Domains: Understand, Quantify, Optimize, Manage
- 9. Know all six core personas
- 10. Showback reports; chargeback actually bills
- 11. RI locks type; SP flexible spend
- 12. Amortized spreads cost; invoice is actual
- 13. Central enablement team drives adoption
FinOps Practitioner
- Practice Questions 202 questions Study Guide 22 topics Cheat Sheet 86 facts Flashcards 50 cards Blogs 1 blog Free CE Podcast