An enterprise organization is preparing to deploy an event-driven telemetry processing engine across multiple Compute Engine managed instance groups in the us-central1 and europe-west1 regions. During an architectural audit 48 hours prior to launch, the lead cloud architect determines that the required target capacity of 640 N2 vCPUs per region exceeds the project's default regional vCPU quota limit of 200 N2 vCPUs. The deployment will be managed automatically via an Infrastructure as Code (IaC) CI/CD pipeline using Terraform. Which proactive strategy should the architect implement to ensure the automated deployment completes successfully without resource allocation failures?
- Submit a proactive regional quota increase request for N2 vCPUs in both target regions via the Google Cloud Console or Cloud Quotas API before executing the Terraform pipeline.Cevap
- BExecute the Terraform pipeline as scheduled and rely on automated pipeline retries, assuming Google Cloud dynamically scales up regional quota limits when provisioning demands increase.
- CGrant the deployment pipeline service account the primitive Owner role at the project level to automatically override regional vCPU quota constraints during resource creation.
- DUpdate the local Terraform state configuration file to manually increment the regional quota capacity parameters before applying the infrastructure plan.
Cevap
Submitting a proactive regional quota increase request for N2 vCPUs in both target regions via the Google Cloud Console or Cloud Quotas API prior to pipeline execution is the correct solution.
Submitting a proactive regional quota increase request ensures that the necessary N2 vCPU capacity is reviewed and allocated by Google Cloud before the deployment pipeline executes. Quotas are project-level and regional constraints enforced by GCP; requesting an increase in advance prevents API errors during automated provisioning.
Adım Adım Çözüm
Anahtar Kavram
Proactive Service Quota Management and Planning