A retail analytics firm provisions automated data processing jobs using temporary Compute Engine Virtual Machines across multiple sub-projects organized under a dedicated folder. The cloud operations team must ensure that no single sub-project exceeds its allocated infrastructure budget or depletes shared regional quota during peak batch processing windows. Which strategy should the Cloud Architect implement to enforce proactive resource limits and governance across these projects?
- Apply consumer quota overrides at the project level to cap maximum VM allocation, and configure Google Cloud Billing budget alerts integrated with Pub/Sub to automate resource capping.Answer
- BMaintain default regional quotas and submit manual quota increase requests to support team operations only after automated out-of-quota error alerts trigger during batch processing.
- CAssign the primitive Owner IAM role to each sub-project's automated service account so it can dynamically reallocate quotas and adjust billing accounts during high workload demand.
- DMaintain independent local Terraform state files on individual operator workstations to manage and sync quota limits and project budget parameters prior to each deployment run.
Answer
Apply consumer quota overrides at the project level to cap maximum VM allocation, and configure Google Cloud Billing budget alerts integrated with Pub/Sub to automate resource capping.
The correct strategy combines consumer quota overrides at the project level with programmatic budget notifications. Quota overrides establish hard upper boundaries on resource utilization per project, while Cloud Billing budgets linked to Pub/Sub enable automated actions to prevent cost overruns.
Step-by-Step Solution
Key Concept
Consumer Quota Overrides & Automated Billing Governance
Estimated Time:1m 30s