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.
An SRE team is configuring Service Level Objectives (SLOs) in Google Cloud Monitoring for two distinct workloads:
You need to define quantifiable, request-based Service Level Indicators (SLIs) in Cloud Monitoring that accurately represent the ratio of good events to valid total events for both workloads.
Which configuration approach should the SRE team use?
Default Availability SLIs in Cloud Monitoring are pre-computed indicators designed for services instrumented with Cloud Service Mesh, Istio on GKE, or App Engine. Cloud Monitoring Uptime Checks periodically probe an external or internal endpoint to verify reachability and HTTP status codes.
Workload 1 were deployed inside Cloud Service Mesh (where default latency SLIs are pre-populated) and Workload 2 exposed a public web health check endpoint rather than a Dataproc batch pipeline.
Arithmetic mean latency calculates the average response time across a dataset ($\sum \text{latency} / n$). A moving average alert evaluates whether the mean rate of a metric over a trailing rolling window exceeds a predefined numeric threshold in Cloud Monitoring alerting policies.
The team only needed operational threshold alerts to wake an on-call engineer during sustained spikes, rather than formal SLI/SLO definitions.
cluster/job/duration below 100 seconds for Workload 2.CPU utilization is an infrastructure health and resource metric that measures host compute saturation. Job duration (cluster/job/duration) measures how long batch jobs spend in active processing states, typically used for freshness or latency SLIs.
cluster/job/duration does not distinguish between successfully completed jobs and failed jobs.The team were conducting infrastructure capacity planning for GKE nodes and defining a data pipeline freshness/speed SLI for Dataproc jobs rather than latency and correctness SLIs.
cluster/job/submitted_count for the total filter and cluster/job/failed_count for the bad service filter for Workload 2.In Google Cloud Monitoring, custom Service Level Indicators (SLIs) allow teams to define compliance criteria when standard pre-computed mesh or platform metrics are not automatically populated. Custom SLIs are constructed as ratios of valid positive (good) events to total valid events using either DistributionCut (for histogram/distribution metrics) or TimeSeriesRatio (for counter/gauge time-series metrics).
< 200 ms). The ratio of request samples falling within this acceptable range compared to all recorded samples defines the request-based latency SLI.cluster/job/submitted_count and cluster/job/failed_count. Using a TimeSeriesRatio structure (goodTotalRatio), Cloud Monitoring computes the ratio of good executions against total valid executions by setting submitted_count as the total service filter and failed_count as the bad service filter.(good events) / (total valid events) across disparate metric formats.This approach directly aligns with SRE best practices and Google Cloud's API structures for service monitoring, allowing both distribution-based latency and counter-based batch job correctness to be monitored within a single, unified SLO framework.
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