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.
An e-commerce organization runs a legacy order processing service that outputs structured JSON logs to stdout. The operations team needs to define a Service Level Indicator (SLI) to track the 95th and 99th percentile latency across different checkout categories without refactoring the application code to add OpenTelemetry or Prometheus metric client libraries.
A sample log payload emitted by the service contains:
{
"message": "Order processed successfully",
"transaction_type": "express_checkout",
"duration_ms": 245.8
}
How should the DevOps engineer configure Google Cloud Observability to generate the required latency SLI metrics?
transform/aco-gke processor to extract latency histograms from standard output.The Google-Built OpenTelemetry Collector is a telemetry proxy that receives OTLP metric, trace, and log streams from application runtimes, processes metadata attributes, and exports data to Cloud Monitoring or Cloud Managed Service for Prometheus.
transform/aco-gke processor is specifically designed to enrich Kubernetes telemetry with App Hub controller labels (top_level_controller_name), not to extract structured JSON fields from application logs into histogram metrics.stdout log printing.The application had already been instrumented with the OpenTelemetry SDK and needed infrastructure metadata enrichment before exporting Prometheus metrics to Google Cloud Managed Service for Prometheus.
jsonPayload.duration_ms as the numeric value, and define a metric label extracting jsonPayload.transaction_type.A distribution log-based metric extracts continuous or discrete numeric values from matched log entries and records them into histogram buckets over time series intervals within Google Cloud Monitoring.
jsonPayload.duration_ms in the metric's value extractor, Cloud Logging parses the numeric duration directly from structured JSON payloads.jsonPayload.transaction_type allows operators to filter, group, and slice latency distributions across different checkout paths.Direct metric instrumentation via SDKs requires code modification, testing, and redeployment. A distribution log-based metric leverages existing JSON logging infrastructure to provide histogram-based percentile metrics immediately at the platform ingestion layer.
A Log Router sink streams log entries asynchronously into external destinations, such as a BigQuery dataset, enabling analytical SQL queries and long-term historical analysis.
The organization required deep retrospective analysis, complex multi-table SQL joins across historical billing and transaction data, or long-term auditing beyond standard logging retention periods.
jsonPayload.duration_ms and another label extracting jsonPayload.transaction_type.A counter log-based metric counts the number of log entries that match a specific Google Cloud Logging filter query over time, producing an incremental integer count of matching log events.
jsonPayload.duration_ms) inside metric labels creates near-infinite distinct label combinations (high cardinality), which degrades monitoring performance and exceeds metric descriptor quotas.The requirement was to build an availability SLI measuring the total number of successful checkout events compared against total transaction requests.
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