Cloud Digital Leader How Google Cloud Resources Are Managed Practice Question
A developer is troubleshooting why a Compute Engine instance cannot start in a specific region. The error indicates a quota limit. Which TWO steps should the developer take?
⚠ Common exam trap
GCDL often tests the misconception that quotas are global or billing-related — candidates pick 'change billing account' or 'delete resources' instead of the correct check-and-request workflow for the specific regional quota.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Check the current quota for the resource in that region via the Quotas page in Cloud Console.
Option A is correct because the Quotas page in Cloud Console (IAM & Admin > Quotas) shows the current usage and limit for each resource per region, letting the developer confirm which quota is exhausted before acting. Option E is correct because when a quota is genuinely too low for the workload, the developer must submit a quota increase request for that specific resource and region, which is then reviewed and approved by Google Cloud support. Together these steps diagnose the exact quota and resolve it through the proper channel. Option B is not appropriate because deleting resources is a destructive action and quota is not 'freed automatically' in a way that guarantees the instance can start; the developer should first identify the quota. Option C is wrong because changing the billing account does not alter regional resource quotas. Option D is wrong because switching to a smaller machine type is a workaround that may not address the actual quota (e.g., if the quota is for CPUs, in-use IP addresses, or persistent disk), and it does not resolve the underlying quota limit.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Check the current quota for the resource in that region via the Quotas page in Cloud Console.
Why this is correct
The Quotas page in Cloud Console displays per-region limits and usage for each resource type, such as vCPUs, static IPs, and persistent disk capacity. When a Compute Engine instance creation fails due to a quota limit, the error message will explicitly indicate a quota exceeded error, and this page confirms the exact metric and current consumption. This is the correct first step because it isolates whether the failure is a quota issue or something else, such as network configuration or billing charges.
- ✗
Delete unused resources in the same region to free up quota automatically.
Why it's wrong here
Deleting unused resources is not a reliable or automatic way to free up quota; quota usage updates asynchronously and may take time to be fully released. Additionally, this approach is reactive and assumes you have underutilized resources, whereas you should first confirm the quota limit via the Quotas page. Even after deletion, some resources like static IP addresses (especially in-use) may still count against quota until they are released properly, so this is not a direct troubleshooting step.
- ✗
Change the project to a different billing account.
Why it's wrong here
Billing accounts are linked to a project for cost tracking and payment, but quotas are scoped per project, per region, and are independent of the billing account. Changing the billing account on a project does not alter its resource limits or the usage that counts against those limits. Therefore, this action would neither resolve a quota limit nor provide any diagnostic information about why the instance creation failed.
- ✗
Use a different machine type that uses fewer vCPUs.
Why it's wrong here
Switching to a machine type with fewer vCPUs is a workaround that may only reduce consumption of one quota dimension (e.g., vCPUs), but it doesn't address the root cause if the quota is exhausted. Moreover, Compute Engine quotas also cover other resources such as memory, GPUs, and regional static IPs, so a lower-vCPU instance might still fail due to a different quota. It also fails to identify the actual limit, making it a non-diagnostic action; the proper fix is to verify and request an increase for the exhausted quota.
- ✓
Request a quota increase for the specific resource in that region.
Why this is correct
After confirming via the Quotas page that you have reached or exceeded a specific regional resource limit, requesting a quota increase is the standard and effective remedy. In the Cloud Console, you can submit a request for the specific resource and region, and Google Cloud often auto-approves many standard quotas within minutes, while others require a review. This directly solves the underlying issue by raising the ceiling for your project, instead of merely working around it.
Visual reference
Go deeper
Related to this question
Learn chapter
Machine Learning on Google Cloud
Key term
Persistent Disk
Persistent Disk is a durable, high-performance block storage service for Google Cloud virtual machines that retains data even after the VM is shut down or deleted.
Key term
IAM
Identity and Access Management (IAM) is a framework of policies and technologies that ensures the right individuals have the appropriate access to technology resources.
About these practice questions
This GCDL question is part of Courseiva's 848-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This GCDL practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the GCDL exam.