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 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?
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.
This option applies AI-generated configuration updates directly to 100% of production workloads and attempts to validate the change using cluster-level node autoscaler behavior while resetting the Gemini Cloud Assist chat session.
The goal was simply to provision additional compute nodes across an entire cluster during a total infrastructure overhaul where progressive delivery and application-level SLI tracking were not required.
This option streams trace data to BigQuery for analytical querying, executes a sudden blue/green traffic switchover, and monitors Gemini Cloud Assist Cloud Audit Logs (geminicloudassist.googleapis.com) to track administrative API activity.
geminicloudassist.googleapis.com audit logs only reveals who interacted with Gemini Cloud Assist APIs (e.g., creating or listing investigations); it provides no insight into application latency, service error rates, or SLO burn rates.The organization required an asynchronous historical compliance audit of how team members interacted with Gemini Cloud Assist investigation resources over a quarterly reporting window.
This option tests the AI recommendations inside an isolated staging environment using synthetic test scripts, uses Gemini to verify resource metadata via Cloud Asset Inventory, and validates the build using automated unit tests.
The change involved updating IAM policies or infrastructure resource definitions that needed static metadata validation and pipeline unit test assertions before being merged into source control.
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