Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A DevOps team manages synthetic monitors in Cloud Monitoring that execute simulated multi-step user workflows against a web application every 30 seconds from multiple regions. Telemetry reveals a 99.9% overall success rate, but the latency distribution exhibits a distinct bimodal pattern where the primary mode finishes in under 80 ms while a secondary mode clusters between 450 ms and 550 ms. Additionally, the synthetic probes are generating significant compute execution costs and adding unnecessary load to backend database dependencies.
Which strategy should the team implement to diagnose the root cause and optimize the synthetic monitoring configuration?
This solution exports raw execution logs into BigQuery for scheduled analysis, restricts synthetic probing to a single region, and drops the synthetic monitor timeout threshold to 200 ms.
The SLA strictly required all operations to fail-fast under 200 ms and the organization only operated in a single cloud region with no need for real-time alerting.
Latency modality analysis evaluates response time distributions via histograms to identify distinct operating conditions (such as cache hits versus disk reads or lock contention) rather than relying solely on simple averages. Optimizing probe intervals and alert conditions adjusts synthetic execution frequencies and threshold aggregation windows to balance rapid failure detection against execution cost and dependency strain.
Evaluating latency histograms rather than arithmetic averages uncovers hidden bimodal behaviors, while tuning probe intervals directly resolves cost and dependency load without compromising SLO visibility.
This approach focuses on identifying virtual machine lifecycle events (such as host maintenance or preemptions) and increases synthetic probe frequency to 10 seconds while applying an alert threshold to the arithmetic mean.
The system suffered from complete VM reboots or guest kernel crashes and required immediate sub-minute infrastructure failover detection regardless of cost.
This option leverages the Network Intelligence Center Performance Dashboard to inspect packet loss and network round-trip time across Google Cloud zones, while configuring an alert strictly on HTTP error status codes.
The application experienced packet drop spikes between compute zones causing hard HTTP 504 timeouts across distributed VPC networks.
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