Unlock the power of your data in the cloud! Get hands-on with Google Cloud's core data services like BigQuery and Looker to validate your practical skills in data ingestion, analysis, and management, and earn your Associate Data Practitioner certification!
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 data engineer is troubleshooting an automated batch pipeline that failed unexpectedly during execution. The engineer needs to examine the pipeline's log entries in Google Cloud to isolate the root cause efficiently.
The engineer has the following requirements:
StudyCerts
StudyCertsERROR or higherconnection_timeout in the message payloadWhich approach should the engineer use in Cloud Logging to accomplish this?
Use the Logs Explorer query editor to specify the time range, set the minimum severity to ERROR, and include the search phrase using Logging query language with uppercase Boolean operators.
Route the pipeline logs from the _Default bucket to a regional logs bucket to automatically filter out warning and notice messages.
Export all historical project logs to an external Cloud Storage bucket using a log sink to run string searches on raw text files.
Create an exclusion filter in the Log Router to permanently discard all informational logs and non-matching errors across the entire Google Cloud project.
Use the Logs Explorer query editor to specify the time range, set the minimum severity to ERROR, and include the search phrase using Logging query language with uppercase Boolean operators.
The Logs Explorer is the primary interface in Cloud Logging designed for viewing, searching, and analyzing log data across Google Cloud resources. The Query Editor within Logs Explorer provides a dedicated workspace where engineers write structured queries using the Logging query language (LQL) to filter massive volumes of log records rapidly.
ERROR or adding a severity >= ERROR clause filters out lower-priority entries (such as INFO or NOTICE), retrieving only critical issues and failures.jsonPayload.message:"connection_timeout" isolates entries containing the exact failure string.timestamp clauses limits the search scope to the specific two-hour incident interval.AND, OR, NOT) for precise matching.Using the Logs Explorer query editor directly within Cloud Logging is the fastest, non-destructive, and most precise method for incident investigation. It avoids modifying system routing configurations, requires no external exports, and provides real-time filtering directly against indexed log entries.
Route the pipeline logs from the _Default bucket to a regional logs bucket to automatically filter out warning and notice messages.
Export all historical project logs to an external Cloud Storage bucket using a log sink to run string searches on raw text files.
Create an exclusion filter in the Log Router to permanently discard all informational logs and non-matching errors across the entire Google Cloud project.