Apptio Cloudability study plan

Apptio Cloudability · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

Cloud Financial Management

Define FinOps principles and how they map to Cloudability's cost management workflow
Label the core Cloudability data pipeline (billing ingestion, normalization, allocation, reporting)
Distinguish showback, chargeback, and cost allocation models and when each applies
Explain the role of tags, accounts, and business mappings in cost visibility

One-page diagram of Cloudability's data flow from cloud bill to cost report, with each stage annotated

Week 2

Configure a sample cost allocation hierarchy using business mappings
Compare amortized vs. unblended vs. blended cost views and select the right one for a scenario
Identify common cost anomalies and the Cloudability views used to surface them
Summarize how budgets and forecasts are set up and monitored

A written walkthrough (300–500 words) of setting up a 3-level cost allocation hierarchy with screenshots or text mockups

Week 3

Categorize optimization levers: rightsizing, reserved instances, savings plans, storage lifecycle, idle resource cleanup
Interpret Cloudability rightsizing and utilization recommendations for compute and storage
Calculate break-even and coverage for commitment-based discounts in a provided scenario
Prioritize a list of optimization actions by estimated savings and effort

Optimization action register with 10 items, each with estimated monthly savings, effort score, and owner

Week 4

Design a tagging taxonomy and enforcement strategy for cost governance
Map Cloudability governance features (budgets, alerts, policies) to control objectives
Draft an escalation path for budget overruns and untagged spend
Distinguish preventive vs. detective controls in cloud cost governance

Governance control matrix mapping 8 controls to Cloudability features, owners, and review cadence

Week 5

Define FinOps personas and their responsibilities in a governance model
Outline the cadence and agenda for a monthly FinOps review
Explain how to measure tagging compliance and allocation accuracy
Identify reporting requirements for finance, engineering, and product stakeholders

FinOps operating model one-pager with personas, meeting cadence, and key metrics

Week 6

Define unit economics metrics (cost per transaction, per customer, per environment) and their inputs
Map cloud cost data to business KPIs using allocation and tagging
Build a unit cost model for a sample application with fixed and variable cost components
Explain how to trend unit costs over time and separate volume effects from efficiency effects

Unit economics model spreadsheet for a sample app, showing cost per transaction and month-over-month trend decomposition

Week 7

Interpret unit cost variance and attribute it to price, volume, and mix
Design a dashboard that combines cost, usage, and business metrics
Evaluate trade-offs between cost efficiency and performance/reliability
Prepare a narrative linking unit economics to business outcomes for an executive audience

Executive summary (1 page) with 3 unit economics insights and recommended actions

Week 8

Review all four domains using a practice scenario spanning allocation, optimization, governance, and unit economics
Identify weak areas from practice and create a targeted review list
Rehearse explaining Cloudability concepts and trade-offs aloud
Confirm familiarity with key terms and workflows across domains

Completed 20-question self-assessment with score by domain and a one-page remediation plan for any domain below 80%

Week 2: Can explain Cloudability's cost data flow and allocation model without notes

Week 4: Optimization action register and governance control matrix completed and peer-reviewed

Week 6: Unit economics model produces a defensible cost-per-transaction figure with documented assumptions

Week 8: Self-assessment score of 80% or higher in every domain