Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs a stateful distributed database workload on Google Cloud where persistent volumes are experiencing rapid data growth. In past incidents, unexpected disk saturation led to read-only states and service disruptions.
You need to establish a proactive capacity planning and monitoring framework in Cloud Monitoring to track storage utilization trends, anticipate project storage quota constraints, and resize storage volumes before application availability is impacted.
Which strategy should you implement?
kubernetes.io/pod/volume/utilization at an 85% threshold over a sustained duration, alongside project quota metrics, to trigger automated or proactive storage expansion workflows.This strategy implements proactive capacity tracking by monitoring storage metrics—specifically persistent volume utilization (kubernetes.io/pod/volume/utilization)—in Cloud Monitoring alongside Google Cloud project quota consumption. When volume utilization or quota allocations cross predefined thresholds, automated expansion workflows or engineering escalations are triggered well in advance of disk exhaustion.
kubernetes.io/pod/volume/utilization metric at an 85% threshold over a multi-minute duration (such as 5 minutes) identifies sustained capacity growth rather than temporary, transient spikes.Monitoring actual storage volume utilization metrics directly in Cloud Monitoring provides real-time alerting with configurable aggregation windows and durations. This ensures rapid, automated intervention before physical disk or quota saturation causes application downtime.
This approach uses Cloud Logging sinks to export operational logs to BigQuery, where scheduled batch SQL queries analyze storage entries and send email alerts when projected usage exceeds 95%.
The requirement was to perform long-term financial modeling and multi-month capacity forecasting across an entire enterprise fleet rather than proactive availability monitoring.
This option depends exclusively on Gemini Cloud Assist recommendations in Database Center to identify over-provisioned and idle resources and downsize or adjust database systems.
The organization wanted to audit existing deployments to eliminate waste and identify underutilized, over-budgeted database instances.
container/cpu/request_utilization crossing 85%, assuming storage capacity exhaustion directly mirrors CPU saturation trends.This option relies solely on container CPU request utilization (kubernetes.io/container/cpu/request_utilization) as a proxy metric to infer storage growth and trigger cluster capacity scaling.
The primary goal were to auto-scale stateless compute workers based on processing bottlenecks rather than planning storage capacity for stateful persistent volumes.
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