What's changed: Created Professional Cloud DevOps Engineer Chapter 5 (Domain 5 "Optimize": APM performance collection, Active Assist insights/recommendations, recommenders (cost/security/performance/manageability/reliability); FinOps = Spot VMs/CUD/SUD/network tiers, utilization/rightsizing, observability cost, per-workload optimization for GKE/Cloud Run/Compute Engine).
5.2FinOps and optimizing workload costs
Understand FinOps practices: Spot VMs, committed-use discounts (CUD) and sustained-use discounts (SUD), network tiers, optimizing resource utilization, observability costs, leveraging recommenders, and optimizing GKE/Cloud Run/Compute Engine workload costs.
FinOps is the culture and practice where engineering and finance collaborate to continuously optimize cloud cost. Combine discounts, purchase options, and utilization to cut waste while preserving SLOs.
5.2.1Discounts, purchase options, and network tiers
| Lever | Key point |
|---|---|
| Spot VMs | Deep discount, preemptible—for fault-tolerant/batch |
| Committed-use discounts (CUD) | Commit 1/3-year usage for a discount |
| Sustained-use discounts (SUD) | Automatic discount for sustained use |
| Network tiers | Premium/Standard trade performance vs cost |
Run fault-tolerant/batch workloads that tolerate interruption on Spot VMs for deep discounts. Lower steady capacity with committed-use discounts (CUD) (1/3-year commitments); sustained-use discounts (SUD) apply automatically to long-running resources. Choose egress network tiers (Premium/Standard) to trade performance vs cost. Map "interruptible batch = Spot VMs" and "steady-use discount = CUD."
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.