Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization runs Cloud SQL and Cloud Spanner databases in a single Google Cloud project in us-central1 and plans to expand into europe-west1. During peak automation activity, two quota issues occur:
429 rateLimitExceeded errors calling SqlInstancesService.Get in us-central1, while global VPC networking quotas in the project are near capacity.us-central1 instance configuration fails immediately and still fails after waiting 10 minutes.Which statement accurately distinguishes these quota behaviors and their regional versus global constraints?
Get is a global rate quota that resets daily at midnight Pacific Time across all regions, whereas Spanner node limits are regional allocation quotas that reset automatically when existing nodes are idle.This option assumes that SqlInstancesService.Get belongs to a daily, globally scoped rate quota and that Cloud Spanner allocation quotas automatically replenish whenever provisioned nodes experience low CPU utilization.
Get: Cloud SQL Admin API Get requests are enforced per minute, per user, and per region, refilling automatically every 60 seconds—not daily at midnight Pacific Time. Only per-day quotas reset at midnight Pacific Time, and only Cloud SQL's Default API category (such as SqlFlagsService.List and SqlTiersService.List) is global.Connect, Get, List, Mutate, Default per region) enforce separate limits per region, per user, per minute.429 errors even when project-level console graphs show unused aggregate quota.The Cloud SQL issue involved a daily rate quota resetting at midnight Pacific Time (or a global Default category API call like listing tiers) rather than SqlInstancesService.Get, and the Spanner issue required deleting unused instances rather than waiting for idle capacity.
To diagnose per-user 429 errors in Cloud SQL, engineers inspect the serviceruntime.googleapis.com/api/request_count metric in Metrics Explorer filtered by response_code = 429 and grouped by credential_id.
Get is a regional rate quota that resets every 60 seconds, while Spanner nodes and VPC networking resources are allocation quotas—meaning europe-west1 has separate regional quotas but shares the global networking pool.Google Cloud enforces rate quotas to control how quickly you consume an API or service over a rolling or fixed time window, and allocation quotas to cap the total amount of provisioned resources your project holds at any given moment. In addition, quota scopes determine whether usage in one location reduces availability elsewhere:
us-central1 does not consume capacity in europe-west1.SqlInstancesService.Get (429 rateLimitExceeded): Cloud SQL Admin API Get operations belong to a per-minute, per-user, per-region rate quota. Because it refills automatically over 60-second intervals, waiting a minute or applying exponential backoff resolves transient bursts. Furthermore, because it is regionally scoped, the us-central1 exhaustion does not block Get requests targeting europe-west1.europe-west1 within the same project still draws from this nearly exhausted global pool.This option correctly pairs each database error with its true quota mechanism—regional rate quota for Cloud SQL Get calls and allocation quotas for Spanner nodes and VPC networking—while accurately explaining why europe-west1 gains fresh regional capacity yet remains constrained by project-wide global networking quotas.
Get and Spanner nodes are both regional rate quotas that refill after 60 seconds, while VPC networking is an unchangeable system limit that blocks expansion into europe-west1.This option treats Cloud Spanner node capacity as a time-based rate quota and classifies VPC networking quotas as fixed system limits that can never be adjusted.
sqladmin.googleapis.com/get per minute) and reset automatically.No such real-world GCP scenario exists where Spanner node capacity refills every 60 seconds, though a similar blocker would occur if you hit a hard system limit—such as Cloud SQL's maximum 64 TB storage ceiling or Spanner's 20-partition geo-partitioning limit—which cannot be raised by a quota request.
Confusing quotas with system limits leads teams to unnecessarily split architectures across new projects when a simple quota adjustment request would resolve a global networking bottleneck.
Get and Spanner node limits are global allocation quotas shared across us-central1 and europe-west1, so expanding into europe-west1 will immediately fail unless you create a new Google Cloud project.This option classifies both Cloud SQL API Get limits and Cloud Spanner node limits as global allocation quotas, implying that every resource in a single project competes for one global pool regardless of region.
SqlInstancesService.Get is a rate quota measuring API calls per minute, not an allocation quota measuring persistent resources.Get requests nor regional Spanner node limits share a global pool with europe-west1. Cloud SQL Get quotas are tracked per region, and Spanner node quotas apply per instance configuration (where us-central1 and europe-west1 have distinct regional configurations).europe-west1 within the same project will not immediately fail due to us-central1 regional quotas—you only need to address the global VPC networking allocation quota.us-central1 leaves europe-west1 regional quotas untouched.Both failures were caused strictly by project-wide global limits—such as reaching the maximum instances per project limit in Cloud SQL or exhausting a global networking quota—with no option to request a quota increase before deploying.
Distinguishing regional from global quotas prevents unnecessary project sprawl when multi-region expansion only requires raising a global networking limit or switching to dedicated service accounts.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated