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 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?
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.This configuration enables the Gemini Cloud Assist API and grants permissions to view Google Cloud resource metadata via Cloud Asset Inventory (roles/cloudasset.viewer) and metric telemetry via Cloud Monitoring (roles/monitoring.viewer).
roles/cloudasset.viewer allows queries regarding resource inventories, policies, and configurations.roles/monitoring.viewer allows querying time-series metrics and dashboard alerts, but not distributed request traces in Cloud Trace.The goal was strictly to ask Gemini questions about cloud resource configurations and metric-based alerting thresholds rather than distributed request tracing.
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.
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.This configuration enables the native tracing API and grants broad administrative permissions over Gemini workspace settings (roles/cloudaicompanion.settingsAdmin) along with full administrative control over Cloud Trace (roles/cloudtrace.admin).
geminicloudassist.googleapis.com, which is required for Gemini Cloud Assist features to function in the Google Cloud console.roles/cloudaicompanion.settingsAdmin grants permissions to manage organization and project settings rather than execute conversational analysis.The scenario required a security lead to configure prompt/response metadata logging sinks and administer trace retention policies across the project.
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.This option configures Developer Connect and attempts to provide trace access by having end users impersonate a service account assigned the Cloud Trace Agent (roles/cloudtrace.agent) role.
cloudtrace.traces.patchTraces) designed for application runtimes or OpenTelemetry collectors to write spans into Cloud Trace. It does not permit reading or analyzing trace data.roles/cloudtrace.agent cannot be used to query or display traces.You were configuring an automated continuous integration pipeline or external telemetry daemon running on-premises to push span data to Google Cloud.
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