A healthcare technology enterprise operates a multi-project Google Cloud environment with steady-state core web services alongside bursty, fault-tolerant batch analytics workloads. The organization needs to establish FinOps governance to improve cost transparency across business units and optimize compute spend without impeding development velocity. Which TWO architectural and governance strategies should the Cloud Architect recommend?
- Configure detailed Cloud Billing export to BigQuery and implement custom dashboards to enable chargeback and showback reporting using standardized resource labels.Cevap
- Purchase Committed Use Discounts (CUDs) for predictable steady-state core workloads while utilizing Spot VMs for bursty, fault-tolerant batch processing.Cevap
- CPurchase 3-year standard Committed Use Discounts (CUDs) to cover all anticipated compute capacity, including short-term, highly variable batch analytics workloads.
- DMigrate all simple, stateless web backends to a dedicated multi-zone Google Kubernetes Engine (GKE) cluster to maximize node density and lower compute overhead.
- EAssign the Owner primitive IAM role to team leads across project billing accounts so they can manually manage resource allocation and enforce financial limits.
Cevap
The architect should recommend exporting detailed Cloud Billing data to BigQuery for label-based showback/chargeback governance, and combining Committed Use Discounts (CUDs) for steady-state baselines with Spot VMs for variable, fault-tolerant workloads.
Combining BigQuery billing exports with standardized labels provides complete financial visibility and enables precise chargeback capabilities across organizational boundaries. Additionally, pairing Committed Use Discounts for predictable baseline services with Spot VMs for fault-tolerant batch workloads achieves optimal financial efficiency across different usage profiles.
Adım Adım Çözüm
Anahtar Kavram
FinOps Cost Governance and Compute Cost Optimization