A cloud engineering team is expanding a compute-intensive microservices application in project `ecommerce-inventory-prod`. During rollout, the team discovers that deploying additional virtual machine instances in the `us-central1` region will exceed the project's regional Compute Engine `CPUS` resource quota. Which TWO valid strategies can the team use to resolve this regional quota constraint? (Select TWO.)
- Submit a formal quota increase request for regional Compute Engine CPUS in us-central1 via the Google Cloud Console Quotas page.Answer
- Deploy the additional microservice virtual machine instances into an alternate region such as us-east1 where regional quota is available.Answer
- CIncrease the billing account monthly budget alert limit to automatically raise the regional compute CPU ceiling.
- DCreate a secondary Virtual Private Cloud network within us-central1 to reset the project's regional CPU quota limit.
Answer
The correct strategies are submitting a quota increase request for regional Compute Engine CPUs in us-central1 via the Cloud Console, and deploying additional virtual machine instances into an alternate region with available quota.
The correct choices recognize that Compute Engine CPU limits are enforced per project per region. Submitting a quota request via the Cloud Console Quotas interface is the standard procedure to officially raise a regional CPU limit. Alternatively, distributing workloads across another region utilizes that region's separate quota pool.
Step-by-Step Solution
Key Concept
GCP Resource Quotas are project- and region-specific boundaries that prevent resource exhaustion. They must be managed via formal quota requests or multi-region resource distribution.