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.
During a major release window, your team receives an alert indicating an increased Service Level Objective (SLO) latency budget burn rate across a critical microservices application on Google Cloud. You run a Gemini Cloud Assist Investigation, which surfaces an anomaly summary hypothesizing that a sudden spike in database CPU utilization was caused by a concurrent configuration update applied via Config Sync.
How should you critically evaluate and validate this AI-generated root-cause hypothesis before initiating remediation?
This approach modifies the application's Service Level Indicators (SLIs) and alerting thresholds in Cloud Monitoring to accommodate the elevated latency and database load, treating the AI-identified anomaly as the new normal operational baseline.
The service had undergone an intentional architectural overhaul where higher latency was pre-negotiated and approved as acceptable within updated business agreements.
This approach attempts to eliminate artificial intelligence output variance by repeatedly executing the Gemini Cloud Assist Investigation until identical outputs are achieved across consecutive runs.
The investigation tool were a deterministic, static rules engine where non-deterministic outputs indicated a transient API communication failure.
This approach accepts the top-ranked hypothesis from Gemini Cloud Assist unconditionally and executes an immediate rollback of the recent Git repository commit managed by Config Sync without validating telemetry.
The DevOps team had already inspected query profiling and distributed tracing data to confirm that queries introduced in that specific commit directly generated database CPU saturation and caused the SLO breach.
Gemini Cloud Assist Investigations analyze multi-signal telemetry—including metrics, logs, and resource configurations—to surface ranked observations and probabilistic hypotheses regarding system anomalies. However, generative AI models produce probabilistic hypotheses that must be verified against actual system telemetry before executing high-impact remediation actions.
Gemini Cloud Assist provides accelerated diagnosis and initial triage, but SRE and DevOps engineering standards require verifying generative AI outputs against deterministic operational telemetry (metrics, traces, and audit logs) prior to applying corrective actions.
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