Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
A DevOps engineer is troubleshooting intermittent tail latency spikes for an API service deployed across multiple Compute Engine VM instances in the us-central1 region.
The engineer needs to configure a chart in Cloud Monitoring Metrics Explorer that meets the following requirements:
us-central1 zone.environment set to production.How should the engineer configure the query parameters in Metrics Explorer?
Configure two filter criteria using logical AND: zone =~ "us-central1-.*" and environment = "production". In the Aggregation section, select the function "99th percentile", select "zone" in the group-by field, and set the alignment interval to 5 minutes.
Configure a single resource filter zone = "us-central1". In the Aggregation section, select "Sum", add "environment" to the group-by field, and set the alignment interval to 5 minutes.
Set the Aggregation element to "Unaggregated" with group-by set to "None". In the Filter section, apply zone !=~ "^us.*" and environment != "production".
Configure two separate filter criteria using logical OR: zone = starts_with("us-central1") or environment = "production". In the Aggregation section, select "Mean", leave the group-by field empty, and set the interval to 5 minutes.
Configure two filter criteria using logical AND: zone =~ "us-central1-.*" and environment = "production". In the Aggregation section, select the function "99th percentile", select "zone" in the group-by field, and set the alignment interval to 5 minutes.
This configuration applies multi-dimensional filtering, statistical alignment, and cross-series grouping directly within the Cloud Monitoring Metrics Explorer interface to isolate and analyze high-percentile tail latency per zone.
us-central1 zones: Metrics Explorer supports RE2 regular expressions via the =~ comparator. Specifying zone =~ "us-central1-.*" matches all zones within the region (e.g., us-central1-a, us-central1-b, us-central1-c, us-central1-f).environment = "production" refines the query. When multiple filter criteria are provided in Metrics Explorer, they are automatically joined with a logical AND, meaning only time series matching both criteria are included.zone reduces high-cardinality instance-level time series into clean, actionable regional zonal baselines.This approach directly leverages Cloud Monitoring's native reduction and alignment pipeline without requiring custom client-side processing, allowing the engineer to spot zonal anomalies in tail latency rapidly.
Configure a single resource filter zone = "us-central1". In the Aggregation section, select "Sum", add "environment" to the group-by field, and set the alignment interval to 5 minutes.
Set the Aggregation element to "Unaggregated" with group-by set to "None". In the Filter section, apply zone !=~ "^us.*" and environment != "production".
Configure two separate filter criteria using logical OR: zone = starts_with("us-central1") or environment = "production". In the Aggregation section, select "Mean", leave the group-by field empty, and set the interval to 5 minutes.