Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
Your e-commerce application running on Google Kubernetes Engine (GKE) is experiencing intermittent latency spikes during peak checkout traffic. You use Gemini Cloud Assist to analyze distributed trace spans in Cloud Trace, and it identifies a significant latency bottleneck in the downstream inventory service, suggesting database connection pooling optimization and an in-memory cache layer.
Before adopting these recommendations across the entire production environment, you need to validate the AI findings against other Google Cloud observability signals, safely test the optimization, and objectively measure its impact on your Service Level Objectives (SLOs).
Which workflow should you follow to validate and implement these optimizations?
Deploy the recommended connection pool and caching configurations immediately across all production replicas, clear the Gemini chat session history, and observe the GKE cluster autoscaler metrics to confirm node scaling.
Create an isolated staging environment replica with synthetic traffic, apply the optimizations, use Gemini Cloud Assist to inspect Cloud Asset Inventory metadata, and rely on unit test suites to confirm resolution.
Cross-reference the trace span durations with database CPU/connection metrics in Cloud Monitoring and query logs in Cloud Logging; deploy the suggested changes to a canary subset of traffic; and track latency SLIs and error budget burn rate against your target SLOs.
Export Cloud Trace data to BigQuery, run scheduled queries to calculate span latencies, execute an immediate blue/green traffic switchover, and monitor Cloud Audit Logs for geminicloudassist API write events.
Deploy the recommended connection pool and caching configurations immediately across all production replicas, clear the Gemini chat session history, and observe the GKE cluster autoscaler metrics to confirm node scaling.
Create an isolated staging environment replica with synthetic traffic, apply the optimizations, use Gemini Cloud Assist to inspect Cloud Asset Inventory metadata, and rely on unit test suites to confirm resolution.
Cross-reference the trace span durations with database CPU/connection metrics in Cloud Monitoring and query logs in Cloud Logging; deploy the suggested changes to a canary subset of traffic; and track latency SLIs and error budget burn rate against your target SLOs.
This workflow represents the Google Cloud Site Reliability Engineering (SRE) best practice for validating AI-assisted diagnostics and safely executing performance optimizations in production systems. It combines multi-signal observability validation, progressive canary deployment, and quantitative Service Level Indicator (SLI) / Service Level Objective (SLO) evaluation.
Generative AI models can occasionally suggest plausible but suboptimal configurations. By systematically corroborating trace findings across the metrics and logs stack and validating the changes via a controlled canary rollout measured against SLIs/SLOs, the engineering team maintains strict reliability guardrails while benefiting from AI-assisted troubleshooting.
Export Cloud Trace data to BigQuery, run scheduled queries to calculate span latencies, execute an immediate blue/green traffic switchover, and monitor Cloud Audit Logs for geminicloudassist API write events.
StudyCerts
StudyCerts