Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization manages a multi-region Shared VPC environment under a dedicated production folder. Ahead of a peak traffic event, you must implement proactive network quota monitoring and automated capacity management with the following requirements:
production folder, while respecting existing manual quota caps.Which operational configuration should you implement?
compute.googleapis.com/network_endpoint_write_requests) without location grouping, and remove all consumer overrides so the Service Limit Recommender automatically raises quotas by 20% at 80% usage.This option mixes Capacity Planner, legacy global API rate metrics, and the Service Limit (Quota) Recommender while removing protective consumer overrides.
compute.googleapis.com/network_endpoint_write_requests measure API request rates rather than resource allocation counts, and regional Compute Engine APIs have migrated to *_per_region metrics. Omitting location grouping prevents isolating which specific region is approaching exhaustion, and filter-based alerts cannot calculate the 80% usage-to-limit ratio.This approach would be appropriate if the objective were forecasting VM, disk, and GPU hardware reservations in Capacity Planner while reviewing 30-day advisory recommendations manually before a seasonal event.
Automatic proactive quota increase submission (typically 10–20%) is specifically a capability of the Quota Adjuster, not the Service Limit Recommender, and Quota Adjuster natively respects manual quota caps without requiring their removal.
serviceruntime.googleapis.com/quota/rate/net_usage with a threshold condition on quota/exceeded, enable Quota Adjuster at the organization level via the Cloud Quotas API, and apply admin overrides across all production projects so Quota Adjuster increases override existing caps.This option attempts to combine PromQL rate-quota alerting with a secondary threshold condition in a single policy, enable Quota Adjuster across the entire organization, and use admin overrides to force quota adjustments.
serviceruntime.googleapis.com/quota/rate/net_usage tracks API rate quotas (delta metrics measured per minute or per day), whereas forwarding rules, firewall rules, and dynamic routes are allocation quotas tracked by serviceruntime.googleapis.com/quota/allocation/usage.production folder, and it still omits project-level QuotaPreference automation for quotas not supported by Quota Adjuster.A single-condition PromQL policy using serviceruntime.googleapis.com/quota/rate/net_usage with increase(...[1m]) would be correct if the goal were strictly monitoring API rate-limit consumption (such as Compute Engine read/write calls per minute) across a single condition.
Understanding the distinction between allocation metrics and rate metrics, as well as the precedence rules of the Service Quota Model, is essential to avoid misconfigured alerts and blocked capacity increases during traffic surges.
serviceruntime.googleapis.com/quota/exceeded for compute.googleapis.com, enable the Quota Adjuster on the production folder in the IAM & Admin > Quotas & System Limits console page, and configure an automated script to submit folder-level QuotaPreference increase requests via the Cloud Quotas API.This option relies on filter-based error alerting in Cloud Monitoring, console-based Quota Adjuster configuration, and folder-level programmatic quota increase requests through the Cloud Quotas API.
serviceruntime.googleapis.com/quota/exceeded is purely reactive—it only triggers after a workload or provisioning request has already hit 100% of a limit and failed. Furthermore, standard filter-based alerting conditions in Cloud Monitoring cannot compute a ratio between two separate metrics (usage divided by limit), making them unsuitable for dynamic percentage-based alerts across varying regional quota limits.quotaAdjusterSettings) or the gcloud CLI.QuotaPreference operations are intended for quota decrease adjustments (such as imposing stricter caps), not for increasing operational limits.quota/exceeded metrics indicate active service disruption rather than early capacity warning.QuotaPreference resources support quota reductions, whereas increases require targeting individual project numbers.This option would only be partially valid if you solely wanted post-failure notifications on a single project, were configuring Quota Adjuster at the project level in the console, and were using folder-level QuotaPreference calls exclusively to lower quotas for cost containment.
When designing automated quota pipelines for Shared VPC environments, engineers must separate policy governance (enabling Quota Adjuster at the folder level via API or CLI) from quota increase execution (submitting QuotaPreference increase requests per project).
serviceruntime.googleapis.com/quota/allocation/usage to serviceruntime.googleapis.com/quota/limit grouped by project_id, quota_metric, and location (> 0.8), enable the Quota Adjuster on the production folder via the Cloud Quotas API or gcloud, and run an automated workflow that queries QuotaInfo and submits project-level QuotaPreference increase requests.This approach combines PromQL-based ratio alerting in Cloud Monitoring, folder-level Quota Adjuster enablement, and programmatic Cloud Quotas API workflows to deliver proactive visibility and automated capacity scaling across regional and global VPC network resources.
serviceruntime.googleapis.com/quota/allocation/usage by serviceruntime.googleapis.com/quota/limit on the consumer_quota resource (grouped by project_id, quota_metric, and location) accurately computes utilization percentages across both regional and global dimensions and fires alerts at > 0.8 before errors occur.gcloud quotas adjuster settings update --folder applies protection across all projects in the production folder. Crucially, the Quota Adjuster automatically skips any quota that has a manual quota cap.QuotaInfo resource to retrieve current quotaValue and applicableLocations, compares them against Cloud Monitoring usage metrics, and submits QuotaPreference updates at the project level, which is where quota increase requests must be issued for most Google Cloud services.RESOURCE_EXHAUSTED or quota exceeded deployment failures during peak events.Unlike reactive quota/exceeded alerts or console-only configurations, this architecture detects approaching bottlenecks early, leverages managed automatic adjustments where supported, and adheres strictly to Cloud Quotas API hierarchy rules for programmatic increases.
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