Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
A data engineering team operates a critical streaming pipeline running on Google Cloud. During unexpected ingestion spikes, the team needs to be notified immediately if worker compute resources experience severe CPU exhaustion while processing latency simultaneously increases on that specific workload.
The alerting policy must trigger only when both conditions are satisfied concurrently for the exact same underlying resource, preventing false alerts caused by unrelated compute instances.
How should the data engineer configure the alerting policy combiner in Cloud Monitoring?
The AND combiner (configured in the Google Cloud console as All conditions are met even for different resources for each condition) opens incidents when all policy conditions are violated across the project, regardless of whether the violations stem from the same resource.
The operational goal were to detect overall platform saturation where high CPU anywhere in the project combined with any latency spike justified an incident.
Defaulting to AND instead of AND_WITH_MATCHING_RESOURCE is a common misconfiguration in multi-condition Cloud Monitoring policies that leads to misleading notifications.
Custom dashboards in Cloud Monitoring allow visual charting of metric time series and permit converting single-condition charts into alert charts for direct operational visibility.
The requirement were strictly to provide dashboard visualization for on-call engineers to inspect individual single-condition alert thresholds alongside real-time metrics.
While custom dashboards are critical for real-time observability, multi-condition alert correlation must be configured directly within the alerting policy definition using appropriate combiner rules.
The OR combiner (configured in the Google Cloud console as Any condition is met) opens an incident as soon as any single condition within the alerting policy evaluates to true.
The team required an alert whenever either CPU exhaustion or latency degradation occurred independently.
OR combiners are standard for aggregating separate catastrophic failure triggers (e.g., node disk full OR process terminated) rather than correlated dual-symptom alerts.
AND_WITH_MATCHING_RESOURCE is an alerting policy combiner mode in Cloud Monitoring (represented in the Google Cloud console as All conditions are met) that enforces multi-condition evaluation scoped strictly to the same monitored entity.
Using AND_WITH_MATCHING_RESOURCE directly solves the operational risk of decoupled condition evaluation, ensuring on-call engineers are notified solely when a specific pipeline component is degraded across both monitored dimensions.
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