Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
You are developing a high-throughput e-commerce checkout platform running as microservices on Google Kubernetes Engine (GKE). During recent traffic spikes, customers experienced intermittent payment failures and degraded response times, while verbose application logs caused observability costs to surge.
You need to redesign the code instrumentation strategy for Google Cloud Observability to meet the following requirements:
DEBUG logs for successful traffic.Which instrumentation strategy should you implement?
This configuration aggressively discards 95% of all log records indiscriminately at the application layer, outputs the remaining 5% as unstructured text without severity metadata, and restricts metric emission strictly to moments when an exception is thrown.
ERROR logs means critical payment failures and stack traces can be lost before reaching Cloud Logging or Error Reporting. Additionally, emitting unstructured plain-text lines without severity levels or trace identifiers makes filtering in Logs Explorer and querying in Observability Analytics difficult.DEBUG or health-check logs) rather than randomly discarding high-severity ERROR events.There is no valid production scenario where randomly dropping ERROR logs and omitting baseline latency metrics provides reliable diagnostics or consistent performance monitoring.
This strategy depends solely on infrastructure-level system metrics automatically collected by GKE and Cloud Monitoring, turns off all custom application logging, and instructs Cloud Trace to capture every single distributed request from start to finish using 100% head-based sampling.
ERROR logs, Error Reporting cannot aggregate application crashes, and engineers lose visibility into why a payment transaction failed.The environment were a low-traffic development cluster where capturing every trace is inexpensive and the team only needed to troubleshoot node resource exhaustion rather than application errors.
This approach uses OpenTelemetry—an open-source, vendor-neutral instrumentation framework—to emit coordinated metrics, logs, and traces to Google Cloud Observability. It pairs purposeful log levels and event boundaries with continuous metric instrumentation and intelligent trace sampling.
INFO and failures with full stack traces at ERROR ensures Cloud Logging and Error Reporting capture actionable context. Applying exclusion filters on log sinks prevents noisy health checks or DEBUG entries from inflating storage costs.ERROR logs with stack traces are automatically grouped and annotated by Error Reporting.Unlike log-only or infrastructure-only approaches, coordinating OpenTelemetry metrics, structured boundary logs, and tail-based sampling delivers deep application visibility, early anomaly detection, and predictable observability spending.
Logging full payloads at the DEBUG level for every transaction captures maximum per-request detail in Cloud Logging, while log-based alerting policies trigger notifications whenever a specific log entry matches a filter condition. Disabling metrics and traces forces all monitoring and troubleshooting to rely solely on log data.
DEBUG payloads for every successful transaction floods Cloud Logging with high-volume, low-value data, driving up ingestion and storage costs instead of isolating meaningful event boundaries.ERROR log entry causes severe alert fatigue during traffic spikes. Furthermore, without continuous metric data, teams cannot track 95th-percentile latency trends or request rates to detect gradual degradation before outages occur.The requirement were to troubleshoot a low-volume staging environment temporarily or to alert immediately on a rare, critical security audit event rather than monitoring high-throughput production performance.
Effective Google Cloud Observability relies on combining logs, metrics, and traces as complementary signals rather than replacing metrics and traces with verbose logging.
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