An enterprise site reliability engineering (SRE) team is scaling out a high-throughput data processing cluster in region `asia-east1`. While attempting to provision additional Compute Engine instances, deployments fail because the project has reached its regional N2 CPU quota limit. Which TWO actions must the team perform to properly inspect and request an increase for this quota?
- Submit a formal quota increase request for the N2 CPUs metric in region `asia-east1` via the Google Cloud Console Quotas section or Cloud Quotas API.Answer
- Verify that the requesting user holds an IAM role with explicit quota editing privileges, such as Quota Administrator (`roles/servicemanagement.quotaAdmin`).Answer
- CConfigure a Cloud Billing budget alert threshold to automatically raise regional compute quotas once project expenditure reaches 80%.
- DGrant the engineer the Billing Account User role on the linked billing account to automatically elevate quota caps across all child projects.
Answer
The team must submit a formal quota increase request for the regional N2 CPU metric via the Google Cloud Console Quotas UI or API, and ensure that the account performing the request possesses an appropriate IAM role with quota management permissions such as Quota Administrator (`roles/servicemanagement.quotaAdmin`).
To raise a Google Cloud resource quota, an administrator must navigate to the Quotas interface (or use the Cloud Quotas API) to select the specific metric and region, and then submit a formal increase request. Additionally, the user performing this request must have sufficient permissions, which are provided by roles like Quota Administrator (`roles/servicemanagement.quotaAdmin`).
Step-by-Step Solution
Key Concept
GCP Resource Quota Request Workflow and IAM Roles