Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A development team creates a new Google Cloud project for an application that calls the Cloud KMS API and other non-default Google Cloud services. During initial setup, they want to verify that the required services can be enabled and ensure the application will not fail with HTTP 429 (RESOURCE_EXHAUSTED) errors during peak traffic.
The team needs to complete the following tasks:
Which approach should the team take?
This option relies on Capacity Planner's Quota Adjuster to automatically submit quota increases on a brand-new project and attempts to modify system limits through the quota editing workflow.
roles/servicemanagement.quotaAdmin) and Capacity Planner Viewer.An established project with active billing and sufficient historical usage data wanted automated, proactive quota increase submissions for supported resources, and the bottlenecks were adjustable quotas rather than fixed system limits.
Developers often use the terms quota and limit interchangeably. Knowing that only quotas can be adjusted—and that Quota Adjuster depends on prior usage telemetry—prevents wasted troubleshooting during new project rollouts.
roles/servicemanagement.quotaViewer) to raise project limits.This option attempts to bypass project-level limits by splitting microservices into unbilled projects, using Cloud Endpoints quota overrides, and relying on the Quota Viewer role to request higher limits.
roles/servicemanagement.quotaViewer) only permits viewing quotas; it lacks the serviceusage.quotas.update permission required to modify quotas or submit increase requests.roles/servicemanagement.quotaAdmin), Project Editor, Project Owner, or a custom role containing serviceusage.quotas.update.You were an API provider hosting a custom backend behind Cloud Endpoints and wanted to raise a rate limit override for a specific external consumer project while granting read-only quota visibility to auditors.
While isolating high-volume resources into separate projects is a valid scaling pattern when single-project quotas are shared across teams, it never eliminates the need for active billing or proper Quota Administrator permissions.
gcloud beta billing projects describe that billingEnabled is true and the linked Cloud Billing account is active, monitor API consumption under APIs & Services > Metrics for the Cloud KMS API, and have a principal with the Quota Administrator (roles/servicemanagement.quotaAdmin) role submit an Edit Quotas request on the Quotas page.This workflow combines Cloud Billing verification, API usage telemetry, and project-level quota management to ensure that enabled Google Cloud services remain operational and properly scaled for application traffic.
gcloud beta billing projects describe PROJECT_ID confirms both the presence of a billingAccountName and billingEnabled: true (indicating the account is neither unlinked nor suspended).roles/servicemanagement.quotaAdmin)—which includes serviceusage.quotas.update and cloudquotas.quotas.update—can submit an Edit Quotas request on the Quotas & System Limits page.RESOURCE_EXHAUSTED (429) errors affect users.Unlike relying on unverified billing links, Compute Engine–specific CLI checks, or premature automation, this approach directly validates billing state, observes the specific API's consumption metrics, and uses the exact IAM role designed for adjusting adjustable project quotas.
gcloud compute regions describe.This option attempts to use Billing Account Viewer permissions to attach a billing account, assumes billing activation removes API quotas, and uses a Compute Engine CLI command to inspect limits for the Cloud KMS API.
roles/billing.user) or Billing Account Administrator on the billing account plus project-level billing assignment permissions. Furthermore, linking a closed or suspended billing account leaves billingEnabled: false, preventing non-default APIs from operating.gcloud compute regions describe displays Compute Engine regional resource quotas (such as CPUs or external IPs), not request-rate consumption for the Cloud KMS API.You only needed read-only visibility into billing account associations using Billing Account Viewer, and you specifically wanted to inspect regional Compute Engine quotas with gcloud compute regions describe rather than Cloud KMS API usage.
A common misconception is that upgrading from a free tier or linking a billing account eliminates quotas. In practice, billing enables access to paid APIs, while Cloud Quotas continues to enforce rate and capacity ceilings per project.
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