FinOps Certified Engineer study plan

Define container cost attribution in your own words and map how namespaces, pods, nodes, and labels each affect chargeback

Explain why node-level billing hides per-pod cost and describe the shared-cost allocation problem for idle and system capacity

Sketch a cluster cost model that separates requests, actual usage, and allocated overhead for a sample workload

List the Kubernetes cost primitives (requests, limits, QoS classes, resource quotas) and state what each one does to spend

Compute per-pod cost from node price, node capacity, and pod resource requests, then compare it to usage-based cost for the same pod

Distinguish over-provisioned requests from genuine usage spikes and describe the billing consequence of each

Explain how horizontal and vertical autoscaling change the cost curve, including scale-down delay and minimum replica floors

Identify which workload types (batch, stateful, daemonset, sidecar) distort naive per-pod cost allocation

Apply the FinOps allocation hierarchy to containers: account, cluster, namespace, workload, team, and environment

Design a labeling and tagging standard that survives autoscaling and ephemeral workloads, and name the failure modes of each label source

Describe how to treat shared services such as ingress, service mesh, logging agents, and monitoring stacks in allocation

Explain showback versus chargeback and choose the right one for a given organizational maturity level

Diagnose the top container waste patterns: idle replicas, oversized requests, missing limits, orphaned persistent volumes, and long-lived dev clusters

Propose a rightsizing recommendation process that uses percentile usage data rather than averages

Explain how bin packing and node autoscaling interact, and when consolidation saves money versus when it risks disruption

Describe unit economics for containers, such as cost per request, cost per tenant, or cost per build minute

State the FinOps Framework principles and lifecycle phases and explain how each phase produces a different engineering artifact

Map the FinOps personas (engineering, finance, procurement, product, leadership) to the container decisions each one owns

Explain the relationship between FinOps, ITAM, ITFM, and FinOps for SaaS, and where container cost sits in that landscape

Describe how budget, forecast, and variance analysis work in a cloud context and how commitment coverage changes the forecast

Explain how commitment-based discounts work for compute and how coverage and utilization targets are set

Describe the tradeoffs between on-demand, committed, and spot capacity for containerized workloads, including interruption handling

Build a simple cost anomaly detection approach and state the threshold and response path for each severity

Explain how to forecast spend for a workload that scales with traffic, and name the assumptions that break the forecast

Integrate container cost data into the broader cloud bill narrative and reconcile the two views to within a stated tolerance

Design a FinOps reporting cadence with the right audience, metric, and decision for each recurring report

Explain how to run a unit-economics review with an engineering team and what evidence makes a rightsizing change stick

Identify automation opportunities in container cost management and the guardrails each one needs

Recall and apply key definitions, lifecycle phases, and container cost concepts under timed conditions

Diagnose scenario questions that mix allocation, rightsizing, commitment, and forecasting concerns and separate the dominant issue from the distractors

Explain your reasoning aloud for ten practice scenarios to expose gaps in how you justify an answer

Close remaining weak areas by rewriting your own notes for the three topics you scored lowest on