Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team deploys a web service on Google Cloud that outputs structured logs to Cloud Logging for every incoming API request. You are tasked with creating custom log-based metrics to improve system observability.
Your monitoring setup must satisfy two specific requirements:
Which combination of log-based metric types should you configure in Cloud Logging?
This option inverts the roles of distribution metrics and counter metrics, using distribution metrics for discrete error counting and counter metrics for latency measurements.
You needed to analyze the distribution of HTTP status code numerical values (e.g., 200 through 504) across all requests, and you only needed to count the total aggregate seconds of server execution time rather than statistical percentiles.
Cumulative metrics and Summary metrics are conceptual metric kinds and types used in specific monitoring frameworks (such as OpenTelemetry or Prometheus client libraries), where cumulative describes a metric value that increases monotonically over time, and summary pre-calculates quantiles client-side.
gcloud logging metrics create, the available types are explicitly categorized as Counter and Distribution metrics.You were configuring client-side Prometheus instrumentation libraries directly within application code rather than configuring native log-based metrics in Cloud Logging.
In metric data models, a gauge metric represents a single numerical value that can arbitrarily go up and down over time, such as instantaneous CPU utilization percentage, current memory usage, or active connection counts.
You were using an external metric exporter reporting instantaneous system states (like queue depth or memory gauge) and tracking total elapsed request duration as a single cumulative sum.
In Google Cloud Observability, log-based metrics extract quantitative metric data from log entries as they are ingested by Cloud Logging. Google Cloud supports two primary user-defined log-based metric types:
jsonPayload.status = 500. This provides an exact rate or count of error events over time, ideal for alerting on threshold breaches.jsonPayload.latency—from log entries and aggregates them into statistical distributions. This enables Cloud Monitoring to compute statistical summaries including mean, 50th percentile (median), 95th percentile (p95), and 99th percentile (p99) latency.Using a counter metric for occurrence frequency and a distribution metric for numerical values is the standard, purpose-built architecture in Cloud Logging and Cloud Monitoring for event tracking and statistical latency analysis.
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