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
Your team manages a multi-tier microservices application running on Google Cloud that is experiencing intermittent latency spikes during high-traffic periods. Distributed tracing is configured across all services, and structured application logs are enriched with standard Google Cloud trace correlation fields.
You need to locate specific slow transactions, inspect the correlated logs for each individual trace span, and perform a historical trend analysis over the past 30 days of log data to identify the downstream database operations causing the degradation.
Which combination of observability tools and query workflows should you implement?
Locate high-latency requests in Cloud Trace, query correlated logs in Cloud Logging using the fully qualified trace="projects/[PROJECT_ID]/traces/[TRACE_ID]" filter, and use BigQuery / Log Analytics to run SQL aggregations across historical log records.
Export trace data from Cloud Trace into Cloud Storage as CSV files, use Dataprep to clean the trace spans, and execute gcloud logging read commands in parallel shell scripts to fetch matching historical logs.
Filter logs in Logs Explorer using custom JSON payload properties such as jsonPayload.trace_id="[TRACE_ID]", inspect trace spans via the Error Reporting console, and export raw logs to Cloud Storage for interactive ad-hoc SQL queries.
Capture real-time logs by initiating a live tailing session filtered on customer IDs, manually inspect latency distributions in Cloud Monitoring Metrics Explorer, and create a Cloud Monitoring log-based metric for 30-day historical query analysis.
Locate high-latency requests in Cloud Trace, query correlated logs in Cloud Logging using the fully qualified trace="projects/[PROJECT_ID]/traces/[TRACE_ID]" filter, and use BigQuery / Log Analytics to run SQL aggregations across historical log records.
This workflow integrates Cloud Trace, Cloud Logging, and BigQuery / Log Analytics into a unified diagnostic pipeline. In Google Cloud, distributed trace spans correlate directly with structured application logs when log entries populate the root trace and spanId fields conforming to the canonical resource name format projects/[PROJECT_ID]/traces/[TRACE_ID].
StudyCerts
StudyCertstrace="projects/[PROJECT_ID]/traces/[TRACE_ID]" in the Logs Explorer retrieves all correlated structured log entries across all microservices involved in that specific distributed request._AllLogs view in Log Analytics, DevOps engineers can run GoogleSQL queries against historical payload structures (such as protoPayload or jsonPayload) and metadata labels over a 30-day window to aggregate latency and isolate systemic downstream database bottlenecks.LogEntry specification for high-performance indexed queries.Using native trace indexing in Cloud Logging combined with SQL analytics in BigQuery avoids operational overhead, ensures millisecond-level log filtering by trace ID, and allows arbitrary historical aggregations that standard metrics dashboards cannot perform.
Export trace data from Cloud Trace into Cloud Storage as CSV files, use Dataprep to clean the trace spans, and execute gcloud logging read commands in parallel shell scripts to fetch matching historical logs.
Filter logs in Logs Explorer using custom JSON payload properties such as jsonPayload.trace_id="[TRACE_ID]", inspect trace spans via the Error Reporting console, and export raw logs to Cloud Storage for interactive ad-hoc SQL queries.
Capture real-time logs by initiating a live tailing session filtered on customer IDs, manually inspect latency distributions in Cloud Monitoring Metrics Explorer, and create a Cloud Monitoring log-based metric for 30-day historical query analysis.