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 organization operates a mission-critical, multi-region checkout API hosted on Google Cloud. You need to establish synthetic monitoring to proactively detect customer-impacting issues before real traffic is disrupted. Your monitoring strategy must fulfill the following operational requirements:
200 OK, contains a specific JSON confirmation key in the response body, and passes TLS certificate validity verification.Which combination of actions should you configure in Google Cloud Monitoring to meet these requirements?
This solution relies on self-managed Compute Engine VMs running ICMP ping commands across regions, extracting network latency via Log-based metrics in Cloud Logging.
200 OK), inspect JSON response body content, or validate application-level TLS certificates.The objective was strictly to measure raw Layer 3 network interconnect latency and packet loss between specific VPC networks.
This solution implements Cloud Monitoring Uptime Checks (synthetic monitors) paired with a metric-based Alerting Policy that evaluates aggregated latency and failure conditions over a designated rolling duration.
200), content matching strings (validating specific JSON payload tokens), and automated TLS/SSL certificate validation to detect expired or invalid certificates.serviceruntime request latencies bucket), configuring the threshold to trigger when latency exceeds 250 ms over a continuous 5-minute rolling alignment window.This approach uses fully managed Google Cloud observability primitives without requiring custom infrastructure, scripts, or cron daemons.
This approach attempts to build a DIY synthetic monitor using a serverless function orchestrated by Cloud Scheduler, exporting execution logs to BigQuery for scheduled batch queries.
You needed historical long-term analytical reporting and forensic audit trails of API transactions rather than real-time operational alerting.
This approach uses PromQL to query internal Google Cloud consumed API latency metrics (serviceruntime.googleapis.com/api/request_latencies_bucket) specifically for backend Firestore service calls and routes raw logs via Pub/Sub.
You were diagnosing internal database latency bottlenecks for backend Datastore or Firestore queries within your application service tier.
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