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 a multi-database platform on Google Cloud using Spanner with Data Boost for analytical queries and AlloyDB for PostgreSQL for operational workloads. During a recent traffic surge, Data Boost queries failed with RESOURCE_EXHAUSTED errors when regional concurrency quotas were exceeded, while an AlloyDB cluster neared its regional vCPU limit.
To prevent availability issues during upcoming peak events, you must:
Which approach should you implement?
Consumer Quota > Quota > Quota exceeded error metric filtered by spanner.googleapis.com/data_boost_quota with a threshold above 0.The Consumer Quota > Quota > Quota exceeded error metric tracks instances where a Google Cloud service actively rejects requests because a project has surpassed its allowed quota. For Spanner Data Boost, exceeding the concurrent ExecuteStreamingSQL and StreamingRead limits triggers RESOURCE_EXHAUSTED errors that increment this counter metric.
Quota exceeded error is greater than 0 only notifies the operations team after the quota is already exhausted and analytical queries have begun failing.quota/exceeded alert cannot warn you at 80% utilization or scale proportionally as a percentage of changing limits.The requirement was strictly to detect and trigger an immediate incident whenever any Spanner Data Boost request was actively rejected due to quota exhaustion, rather than receiving an early warning before failures occur.
Concurrent Quota usage, and configure a filter-based alerting policy with a static threshold value set to 80% of the current regional limit.Filter-based alerting policies in Cloud Monitoring allow you to select a single metric—such as Consumer Quota > Quota > Concurrent Quota usage—filter it by quota_metric (for example, spanner.googleapis.com/data_boost_quota), and trigger an alert when the time series crosses a fixed numeric threshold.
Concurrent Quota usage as a live percentage of serviceruntime.googleapis.com/quota/limit.200 concurrent requests is later raised to 500, a hardcoded threshold of 160 will falsely alert at 32% utilization until an administrator manually updates the policy.You were monitoring a single region with a fixed quota limit that would never be increased, making a static numeric threshold acceptable without dynamic ratio calculation.
The Quota Adjuster is a feature on the IAM & Admin > Quotas & System Limits page that monitors resource consumption and automatically submits quota increase requests on your behalf when usage approaches a limit. The Service Limit Recommender analyzes quota utilization over the past 30 days and generates capacity recommendations when usage nears 80% of a limit.
RESOURCE_EXHAUSTED failures.Your primary goal was long-term capacity planning and automating routine quota increase requests for steady workload growth, rather than configuring real-time proactive alerts for concurrency spikes.
Consumer Quota metrics in Metrics Explorer, then create a PromQL-based alerting policy that divides serviceruntime quota usage by serviceruntime.googleapis.com/quota/limit with a threshold of > 0.8.Evaluating database capacity across Google Cloud requires combining the Quotas & System Limits dashboard with Cloud Monitoring telemetry. Services that support quota metrics—such as Spanner—write serviceruntime time-series data to the consumer_quota monitored resource with a quota_metric label identifying each specific limit. Prometheus Query Language (PromQL) enables mathematical expressions across multiple time series, making it possible to compute real-time utilization ratios dynamically.
AlloyDB API (such as VCPUsUsedPerProjectPerRegion) and databoost (such as DataBoostQuotaPerProjectPerRegion) reveals active regional limits. In Cloud Monitoring Metrics Explorer, selecting the Consumer Quota resource type and filtering by quota_metric (for example, spanner.googleapis.com/data_boost_quota) lets you chart Concurrent Quota usage alongside Quota limit.serviceruntime usage metric by serviceruntime.googleapis.com/quota/limit, aggregated by project_id, quota_metric, and location, with a condition of > 0.8. Whenever consumption reaches 80% in any region, the policy triggers notifications before requests fail.serviceruntime.googleapis.com/quota/limit dynamically, future quota increases require zero manual alert edits.location evaluates every region independently against its own regional limit.RESOURCE_EXHAUSTED errors occur.Unlike filter-based policies that rely on hardcoded numeric thresholds, reactive error alerts that only fire after outages begin, or planning tools that lack real-time spike notifications, PromQL ratio alerting paired with Quotas dashboard and Metrics Explorer visibility satisfies both immediate evaluation and resilient proactive alerting.
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