A cloud operations team manages a stateful database cluster hosted on Compute Engine virtual machines in the region `us-central1`. During a planned scale-out operation, attempting to create additional VM instances fails with an error indicating that the regional `N2_CPUS` quota limit has been exceeded. The database workload requires continuous availability and cannot tolerate unexpected instance terminations. Which action should the team take to resolve this deployment failure in accordance with Google-recommended best practices?
- Submit a formal quota increase request for the N2_CPUS metric in the us-central1 region using the Google Cloud Console or gcloud CLI.Cevap
- BProvision the new database VM instances in an alternate region where unused CPU capacity exists, without requesting a quota modification.
- CReconfigure the new VM instances to provision as Spot VMs so that they run on spare capacity and bypass project CPU quotas.
- DGrant the Project Editor primitive role to the deployment service account so that instance creation requests bypass standard project quota limits.
Cevap
Submit a formal quota increase request for the N2_CPUS metric in the us-central1 region using the Google Cloud Console or gcloud CLI.
Submitting a formal quota increase request for the N2_CPUS metric in the specified region directly addresses the project capacity limitation while maintaining the workload's location and availability requirements.
Adım Adım Çözüm
Anahtar Kavram
GCP Resource Quota Management