A financial data organization is setting up an automated pipeline to provision a cluster of custom Compute Engine virtual machines in the us-east4 region for nightly risk calculation workloads. During the initial deployment execution, the orchestration system fails immediately with a quota constraint error regarding N2_CPUS before any instances can be created. Which action should the Cloud Architect take to resolve this provisioning failure?
- Submit a request to increase the regional N2_CPUS quota for the us-east4 region via the Google Cloud Console before running the deployment.Answer
- BAssign the primitive Owner role to the deployment service account to bypass regional resource limits during automated provisioning.
- CGrant the Service Account Admin role to the compute instance template so it can self-provision additional quota dynamically.
- DMigrate the workload to a Google Kubernetes Engine cluster to automatically bypass Compute Engine regional vCPU quotas.
Answer
Submit a request to increase the regional N2_CPUS quota for the us-east4 region via the Google Cloud Console before running the deployment.
Compute Engine enforces quota limits on CPU cores per region and machine family. When a planned deployment exceeds the available quota, the architect must proactively request a quota increase for that specific region and resource type prior to launching the compute resources.
Step-by-Step Solution
Key Concept
Compute Engine Regional Resource Quotas