Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your database team manages Cloud SQL instances and Backup and DR services within a Google Cloud project. You need to implement an alerting solution that meets the following requirements:
Which configuration should you implement?
Row count threshold condition greater than 0 to query the error logs.A SQL-based alerting policy in Observability Analytics periodically executes a BigQuery SQL query against a log view backed by a linked BigQuery dataset. It evaluates aggregated results over a scheduled lookback window using either a Row count threshold or a Boolean condition.
ERROR severity), rather than inspecting single log entries as they arrive.WHERE timestamp filters because Observability Analytics injects the lookback window filter automatically.You needed to trigger an alert based on aggregate calculations across many log entries over a scheduled interval—for example, alerting only when the percentage of database ERROR logs exceeds a specific ratio or when a row count across a 60-minute window crosses a numerical threshold.
AND NOT operators to exclude the non-impacting event IDs, extract a resource identifier label via a regular expression, and attach a notification channel.A log-based alerting policy monitors Cloud Logging ingestion in real time and triggers an incident in Cloud Monitoring whenever an individual log entry matches a specified Logging query language filter. Unlike metric-based alerts that aggregate numeric time series, log-based alerting policies evaluate each incoming log entry directly against your query criteria.
FAILED backup job appears—even if the event occurs only once.AND NOT and OR inside the alert query (for example, AND NOT jsonPayload.eventId=(10229 OR 42356)) suppresses alerts for known false positives while keeping all log entries retained in Cloud Logging for auditing and troubleshooting.=~ to match dynamic error strings in jsonPayload or protoPayload fields.logEntries.write.For sparse, high-severity database errors and security events that require immediate action, a log-based alerting policy provides the lowest latency, exact log-entry matching, and payload label extraction without requiring BigQuery datasets or metric aggregation pipelines.
0.A log-based metric counts or extracts numeric distributions from matching log entries in Cloud Logging and exports those values as time-series data to Cloud Monitoring. You can then attach a standard metric-based alerting policy to evaluate thresholds over alignment periods.
0 signal indicating recovery.Your primary goal was to monitor long-term trends or rate changes in high-volume database logs—such as graphing the rate of deadlocks or slow queries per minute over weeks—rather than receiving immediate notifications for individual critical errors or security events.
timestamp field as a custom label.This option attempts to use a log-based alerting policy while scoping the query to a specific log bucket, relying on a Cloud Logging exclusion filter to drop unwanted event IDs, and extracting the log entry's timestamp field as a custom notification label.
timestamp breaks alerting: In Cloud Logging, configuring a log-based alerting policy to extract the timestamp label prevents the alerting policy from creating alerts and sending notifications. Any alert policy extracting that label will silently fail to notify.logName, resource.type, and payload fields) and cannot filter by specific log buckets, billing accounts, or organizations.timestamp label, a single log-based alerting policy can create a maximum of 2 new alerts per minute and 20 alerts per day.No configuration combining bucket-level log-based alerts and timestamp label extraction is valid; instead, you should always scope the alert query at the project level using AND NOT in the filter and extract non-timestamp fields like resource.labels or jsonPayload identifiers.
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