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
A DevOps engineer is investigating intermittent HTTP 504 Gateway Timeout errors across a distributed microservices application composed of a Cloud Run frontend service and a Cloud SQL backend instance. The application logs thousands of events per minute in Cloud Logging, making manual correlation challenging.
The engineer needs to formulate an effective natural language prompt in Gemini Cloud Assist to analyze the log data, correlate events across both services, identify performance degradation trends, and determine the root cause.
Which prompting strategy should the engineer use to achieve the most precise and actionable analysis from Gemini Cloud Assist?
Provide a detailed, scoped prompt specifying the relevant resource identifiers, the exact time window of the 504 errors, observed latency symptoms, and request a correlation between Cloud Run request latencies and Cloud SQL connection or query execution logs with ranked hypotheses.
Instruct Gemini in a single prompt to convert all raw application logs into SQL DDL schema definitions and create automated database migration conversion rules.
Prompt Gemini exclusively with Cloud Run HTTP status logs and omit backend database names, relying on Gemini to autonomously infer and query unreferenced backend resources.
Submit an open-ended generic prompt such as "Find all errors across my project logs and fix the downtime" without supplying service names, log timestamps, or error codes.
Provide a detailed, scoped prompt specifying the relevant resource identifiers, the exact time window of the 504 errors, observed latency symptoms, and request a correlation between Cloud Run request latencies and Cloud SQL connection or query execution logs with ranked hypotheses.
Precise prompting involves giving Gemini Cloud Assist specific contextual anchors—including exact resource identifiers, timestamps or operational windows, observed error indicators, and explicit analytical objectives. When troubleshooting complex multi-tier systems, anchoring the model with specific resource contexts allows it to synthesize relevant logs, metrics, and configuration data effectively.
Iterative and detailed prompt formulation provides the model with the necessary parameters to narrow down millions of log entries into a focused timeline of cause and effect, outperforming broad, ambiguous prompts.
Instruct Gemini in a single prompt to convert all raw application logs into SQL DDL schema definitions and create automated database migration conversion rules.
Prompt Gemini exclusively with Cloud Run HTTP status logs and omit backend database names, relying on Gemini to autonomously infer and query unreferenced backend resources.
Submit an open-ended generic prompt such as "Find all errors across my project logs and fix the downtime" without supplying service names, log timestamps, or error codes.