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 team is implementing an observability and root-cause analysis strategy across distributed microservices running on Google Cloud. Distributed trace and span data are ingested into Cloud Trace, and you want DevOps engineers to utilize Gemini Cloud Assist within the Google Cloud console to query trace data, diagnose latency bottlenecks, and identify systemic performance failures.
You need to establish the required API connectivity and implement Identity and Access Management (IAM) role assignments following the principle of least privilege.
Which configuration should you implement?
Enable Developer Connect (developerconnect.googleapis.com), deploy a service account with the Cloud Trace Agent (roles/cloudtrace.agent) role, and grant engineers the Service Account Token Creator (roles/iam.serviceAccountTokenCreator) role.
Enable the Gemini Cloud Assist API (geminicloudassist.googleapis.com), and grant the engineers the Cloud Asset Viewer (roles/cloudasset.viewer) and Monitoring Viewer (roles/monitoring.viewer) IAM roles without trace-specific roles.
Enable the Gemini Cloud Assist API (geminicloudassist.googleapis.com) in the project, and grant the engineers the Gemini Cloud Assist User (roles/geminicloudassist.user) and Cloud Trace User (roles/cloudtrace.user) IAM roles.
Enable only the Cloud Trace API (cloudtrace.googleapis.com), and grant the engineers the Gemini for Google Cloud Settings Admin (roles/cloudaicompanion.settingsAdmin) and Cloud Trace Admin (roles/cloudtrace.admin) IAM roles.
Enable Developer Connect (developerconnect.googleapis.com), deploy a service account with the Cloud Trace Agent (roles/cloudtrace.agent) role, and grant engineers the Service Account Token Creator (roles/iam.serviceAccountTokenCreator) role.
Enable the Gemini Cloud Assist API (geminicloudassist.googleapis.com), and grant the engineers the Cloud Asset Viewer (roles/cloudasset.viewer) and Monitoring Viewer (roles/monitoring.viewer) IAM roles without trace-specific roles.
Enable the Gemini Cloud Assist API (geminicloudassist.googleapis.com) in the project, and grant the engineers the Gemini Cloud Assist User (roles/geminicloudassist.user) and Cloud Trace User (roles/cloudtrace.user) IAM roles.
This solution activates the required Google Cloud backend APIs for generative AI assistance and assigns the least-privilege IAM roles necessary for users to interact with Gemini Cloud Assist while accessing underlying Cloud Trace telemetry.
geminicloudassist.googleapis.com automatically provisions necessary service endpoints (including cloudaicompanion.googleapis.com) so that the project can process conversational assistance and diagnostic workflows.roles/geminicloudassist.user) role provides the principal with the permissions required to interface with the Gemini Cloud Assist chat panel and investigation tools.roles/cloudtrace.user) role allows Gemini to retrieve, analyze, and synthesize distributed trace spans on behalf of the engineer.This approach satisfies all connectivity and authorization prerequisites with minimal administrative overhead and avoids excessive permissions like project-level admin roles.
Enable only the Cloud Trace API (cloudtrace.googleapis.com), and grant the engineers the Gemini for Google Cloud Settings Admin (roles/cloudaicompanion.settingsAdmin) and Cloud Trace Admin (roles/cloudtrace.admin) IAM roles.