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 enterprise operates a distributed microservices architecture deployed across Compute Engine virtual machines, Google Kubernetes Engine (GKE) clusters, and Cloud Run services located in multiple Google Cloud projects. You need to implement a centralized observability strategy in Google Cloud Monitoring to collect and aggregate metrics, logs, and distributed traces from both infrastructure and applications to track Service-Level Objectives (SLOs) and application key performance indicators (KPIs) through unified dashboards.
Which strategy aligns with Google Cloud recommended best practices?
This approach relies on VPC Packet Mirroring to analyze network payloads for performance data, uses log exclusion filters in Cloud Logging to discard informational logs, and streams raw, unaligned time-series points directly into BigQuery every minute to build real-time dashboards.
The primary goal was deep network security packet inspection or threat detection across VPC interfaces rather than distributed application performance monitoring and SLO management.
This approach avoids native managed agents by installing self-managed OpenTelemetry Collector binaries on VMs, running unmanaged Prometheus servers inside GKE clusters, archiving logs to Cloud Storage, and developing custom Cloud Functions to fetch time-series data via API calls for visualization.
The organization had a strict regulatory requirement to maintain fully air-gapped, isolated monitoring infrastructure with zero reliance on cloud-managed observability backends or native console dashboards.
This strategy establishes an end-to-end telemetry pipeline across hybrid and polyglot workloads using Google Cloud's modern observability architecture. It leverages open standards and fully managed services to capture, aggregate, and visualize metrics, logs, and traces without introducing management overhead or vendor lock-in.
This solution relies completely on Google Cloud's native, managed observability tooling and CNCF standards. It removes operational toil associated with managing custom ingestion proxies or manual batch upload scripts while delivering real-time metric evaluation for critical SLOs.
This option couples application code directly to the proprietary Cloud Monitoring API client libraries, isolates monitoring to separate individual projects without multi-project scoping, and restricts operational views to out-of-the-box Google Services dashboards.
The deployment consisted solely of isolated, single-service architectures using basic default GCP services without any cross-project communication, custom application metrics, or custom SLO requirements.
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