A digital media publishing enterprise operates its online platform and content delivery pipeline on Google Cloud. The workload consists of steady-state web API services alongside highly variable, unpredictable batch jobs for media encoding. The organization wants to establish central FinOps governance to increase cost transparency and optimize cloud spending across multiple department projects without introducing operational overhead. Which TWO recommendations should the Cloud Architect propose? (Select TWO.)
- Export detailed Cloud Billing data to a centralized BigQuery dataset across the organization and configure Cloud Billing budgets with Pub/Sub notification channels.Cevap
- BPurchase 3-year standard Compute Engine Committed Use Discounts (CUDs) to cover the full capacity of all media encoding batch jobs.
- Configure Cloud Storage Object Lifecycle Management policies to transition historical media assets to Coldline or Archive storage based on access frequency.Cevap
- DMigrate all simple stateless microservices from Cloud Run to dedicated Google Kubernetes Engine (GKE) clusters to eliminate per-request runtime fees.
- EGrant the primitive Billing Account Admin IAM role to all project leads so each team can manage independent billing accounts.
Cevap
The Cloud Architect should recommend exporting detailed Cloud Billing data to BigQuery combined with Pub/Sub budget notifications, and implementing Cloud Storage Object Lifecycle Management policies to transition aging media files to lower-cost storage classes.
Centralized BigQuery billing export provides granular, organization-wide visibility required for chargeback and cost analytics, while Cloud Billing budget notifications via Pub/Sub enable programmatic governance. Additionally, Object Lifecycle Management automates moving infrequently accessed objects from Standard storage to cheaper Coldline or Archive storage, directly optimizing persistent storage costs.
Adım Adım Çözüm
Anahtar Kavram
FinOps Cost Governance and Lifecycle Optimization