Free FOCP Exam Flashcards

Cloud usage is variable and consumption-based rather than fixed capacity, and provisioning access is decentralized across many engineering teams, so spend can shift hour to hour instead of following a predictable capital budget cycle.

Cloud moves technology spend from upfront capital expenditure, like buying servers, to ongoing operating expenditure paid as usage happens, which changes how finance teams budget, forecast, and approve spend.

It lets engineers self-serve infrastructure instantly, speeding delivery, but it also means many people across the org can generate cost without central review, making real-time visibility essential.

Each provider issues its own invoice with different pricing structures, discount programs, and terminology, so multi-cloud billing requires normalizing the data before it can be compared or reported together.

FinOps is an operational framework and cultural practice that maximizes the business value of cloud, enables timely data-driven decisions, and creates financial accountability through collaboration between engineering, finance, and business teams.

No. FinOps is about maximizing business value from cloud spend, which sometimes means spending more to enable growth and sometimes less, rather than simply minimizing the bill.

Teams need to collaborate; everyone takes ownership of their cloud usage; a centralized team enables FinOps practices; reports should be accessible and timely; decisions are driven by the business value of cloud; and organizations should take advantage of the variable cost model of cloud.

They must work together continuously on cloud spend decisions rather than operating in silos, so cost, engineering, and business priorities are addressed jointly instead of handed off sequentially.

Each team is accountable for its own cloud usage and cost, the same way it already owns the uptime and performance of the services it runs.

Instead of treating cloud spend as fixed, FinOps teams exploit the ability to scale usage up or down instantly, treating cost as a lever that can be tuned in near real time rather than locked in annually.

Practitioner, Engineering, Finance, Leadership, Product, and Procurement — the roles most directly responsible for driving and executing day-to-day FinOps decisions.

The Practitioner drives and coordinates the FinOps practice itself, building reports and facilitating collaboration, while the other core personas execute domain-specific FinOps work like engineering optimization or budget ownership.

Supporting roles such as ITAM, ITFM, ITSM, Security, and Sustainability that intersect with FinOps but are not core to running the day-to-day practice.

Centralized uses one team enforcing consistent governance across the organization, which is slower to scale; Decentralized embeds FinOps responsibility inside each team, enabling faster local decisions but making standards harder to enforce.

A central FinOps team sets standards and tooling while embedded staff in individual business units execute the FinOps work locally — a hybrid between the centralized and decentralized models.

Sustainable cost accountability depends on shared behaviors, like collaboration, ownership, and timely decisions, which reporting tools alone cannot create without changing how teams actually work together.

Understand Usage & Cost, Quantify Business Value, Optimize Usage & Cost, and Manage the FinOps Practice — moving from visibility, to measuring value, to taking action, to sustaining governance.

It collects raw billing and usage data from cloud providers; allocation, reporting, forecasting, and every downstream capability rely on this data being complete and accurate.

It assigns cloud cost to the correct owning team, product, or cost center, usually through tags or allocation keys, so spend can be attributed accurately instead of sitting as one lump invoice.

An unexpected spike or deviation from the expected cost pattern triggers investigation; Reporting and Analytics provides the baseline trend data that makes an anomaly recognizable in the first place.

It expresses cloud cost per business outcome, such as cost per customer or per transaction, so efficiency can be compared over time or against revenue growth rather than looking at raw spend alone.

Forecasting predicts future cloud spend based on usage trends, while budgeting sets the spend targets teams are expected to stay within — a good forecast tells you whether a budget is realistic.

They measure FinOps efficiency and compare it against internal targets or industry peers, turning raw savings numbers into a standard that shows whether performance is actually improving.

Rate Optimization lowers the unit price paid, typically through commitments or discounts; Usage Optimization reduces or rightsizes the actual resources consumed, regardless of price.

Reserved Instances lock in a specific instance type and region as a capacity commitment; Savings Plans commit to a spend amount but flex across instance families and services.

For interruptible, fault-tolerant workloads such as batch processing, where accepting the risk that the resource can be reclaimed at any time earns the steepest possible discount.

It covers rightsizing spend on software licenses and SaaS subscriptions; teams often focus optimization effort on infrastructure and miss this recurring, often-forgotten cost category.

Showback only reports cost back to a team for awareness, with no real billing; Chargeback actually transfers the cost into that team's budget, driving stronger accountability.

It measures organizational FinOps maturity; it is assessed capability by capability because a team can be advanced in allocation while still immature in anomaly management or forecasting.

Executive Strategy Alignment ties cloud spend decisions to overall business strategy and leadership priorities; Governance and Risk enforces the day-to-day spend guardrails and policy compliance that keep the practice on track.

To build cost visibility by allocating spend to owners, reporting it clearly, setting budgets, and benchmarking against peers or historical data.

Inform — budgeting spend expectations is a visibility-building activity that happens before any optimization action is taken.

Benchmarking compares current cost against peers or history to establish where the organization stands; it creates visibility and context, it does not itself change any spend.

Ingested and allocated billing data — without cost properly tagged and attributed to owners, reporting and benchmarking during Inform will be inaccurate or incomplete.

Rate optimization by buying commitments, usage optimization by rightsizing or shutting down idle resources, workload optimization by re-architecting, and waste elimination.

Optimize — waste elimination is an Optimize-phase action that removes idle, unused resources identified during Inform.

Optimize — rate optimization actions like purchasing commitments happen in the Optimize phase, after Inform revealed the usage pattern that justified the commitment.

The Operate phase — it enforces ongoing governance policies, automates corrective action, tracks KPIs against targets, and sustains the collaborative culture over time.

Inform builds visibility once; Operate is about sustaining and automating that discipline continuously, which is exactly what ongoing governance enforcement does.

Inform establishes baseline KPIs and benchmarks for visibility; Operate then tracks those same KPIs continuously afterward to confirm the outcomes are actually sustained over time.

Crawl, meaning manual and basic practice; Walk, meaning partial process automation; and Run, meaning a fully automated, mature practice.

No — maturity is assessed per capability, so an organization can be at Run maturity for allocation while still at Crawl for anomaly management.

Crawl — manual processes with minimal automation are the hallmark of the earliest maturity stage.

Walk has partial process automation already in place; Run has automation fully embedded so the capability operates continuously without manual intervention.

Maturity builds progressively per capability — the visibility and habits established at Crawl and Walk are typically what make automation at Run reliable and trusted.

List Price is the published on-demand rate; Effective Price is the rate actually paid after all discounts, commitments, and negotiated terms are applied.

It spreads an upfront or committed cost evenly across the commitment term, so monthly reports show a smoothed, realistic cost instead of one large spike in the month it was purchased.

Amortized Cost smooths commitment costs over time for consistent reporting; Net Cost is the actual final invoiced amount for that billing period, including one-time charges.

A Tag is a metadata label attached to a resource as a key-value pair; an Allocation Key is the rule used to split a shared or untagged cost across multiple cost centers when no tag applies directly.

The Cost and Usage Report is AWS's detailed billing export, providing the raw usage data that feeds normalization and reporting pipelines across the FinOps practice.