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 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?
zone = "us-central1". In the Aggregation section, select "Sum", add "environment" to the group-by field, and set the alignment interval to 5 minutes.This configuration performs an exact string equality check on the zone label against the string "us-central1" and computes the cumulative sum of latency grouped by environment.
us-central1 is a region name, whereas the resource label zone contains specific zone identifiers such as us-central1-a or us-central1-b. An exact equality match (= "us-central1") will match zero time series and return no data.Sum of latency is mathematically meaningless for understanding response times; sum aggregation is intended for counter metrics like total request count or byte counts.environment instead of zone fails the requirement to compare metrics across different zones.starts_with helper functions.Sum is not a valid statistic for latency distributions or gauges.The metric being measured was total request throughput (request_count) across an environment where the zone label exactly matched the filter string.
zone !=~ "^us.*" and environment != "production".This configuration displays all raw, unaggregated time series individually while using negative regex and inequality filters.
!=~ and != excludes us-central1 and excludes production, matching only non-US zones and non-production environments.Unaggregated and group-by to None plots every single VM instance as an individual line on the chart. This causes high-cardinality noise, fails to calculate the 99th percentile, and does not aggregate per zone.!=, !=~) invert filter matching logic.The objective was to audit every individual non-production VM instance located outside the United States without any time alignment or statistical reduction.
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.
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.This option attempts to filter data by evaluating criteria with a logical OR operation and calculates the overall average (Mean) across all matched instances as a single combined time series.
OR logic between zone and environment would pull in non-production instances from us-central1 as well as production instances located in unrelated regions.Mean averages the latency, which smooths out spikes and hides tail latency anomalies.OR concatenation across different filter dimensions in standard filter mode.The goal were to visualize a single project-wide average latency baseline across either production systems or any service running in us-central1.
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