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.
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?
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].
trace="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.
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.This approach attempts to filter logs using custom application payload attributes (e.g., jsonPayload.trace_id), view distributed traces inside Google Cloud Error Reporting, and execute ad-hoc historical queries against raw log files stored in Cloud Storage.
jsonPayload.trace_id fails to leverage the top-level indexed trace field on the LogEntry object (projects/[PROJECT_ID]/traces/[TRACE_ID]). Without the canonical field, Cloud Trace and Cloud Logging cannot automatically cross-link spans and log entries.The application was only tracking unhandled application exceptions without distributed trace contexts and storing cold archival logs where multi-service correlation was not required.
gcloud logging read commands in parallel shell scripts to fetch matching historical logs.This option involves extracting trace spans into Cloud Storage CSV files, transforming them with Dataprep, and executing scripted gcloud logging read commands to find matching log entries for historical analysis.
gcloud logging read CLI queries over 30 days of historical logs is subject to API rate limits, slow serial pagination, and high network latency compared to native GoogleSQL queries in BigQuery.gcloud logging read command is designed for targeted inspection, not large-scale historical analytics across millions of log records.You needed to export non-standard trace extracts to an external third-party data lake via scheduled batch file transfers.
This option relies on Live Tailing within Cloud Logging for real-time stream inspection, viewing aggregate latency in Cloud Monitoring Metrics Explorer, and defining log-based metrics to track historical latency patterns.
The requirement was to stream incoming logs in real time during a live deployment and create an alerting policy on future error count thresholds.
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