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 DevOps engineering team is standardizing the use of Gemini in the CLI and development environments to synthesize complex gcloud automation scripts and inspect deployment configurations across your Google Cloud estate.
Your organization enforces strict data governance and enterprise security requirements:
Which combination of IAM roles and security controls should you implement?
discoveryengine.googleapis.com, assign the roles/discoveryengine.admin role to a developer Google Group, and configure Access Context Manager to allow unrestricted public IP ingress.This configuration enables the Discovery Engine API (discoveryengine.googleapis.com) and grants full administrative rights (roles/discoveryengine.admin) for Gemini Enterprise search, knowledge agents, and intranet data stores.
cloudaicompanion.googleapis.com).roles/discoveryengine.admin role provides full administrative control over data stores, search engines, and ACL configurations, violating least-privilege access for developers who only need CLI assistance.An enterprise search administrator needed to configure multimodal search connectors and agent engines for unstructured corporate documents in Gemini Enterprise.
roles/editor role at the organization node to developers and disable the cloudaicompanion.googleapis.com API on development projects.This configuration grants the broad, legacy Editor (roles/editor) primitive IAM role at the organization root while turning off the underlying Gemini for Google Cloud API (cloudaicompanion.googleapis.com).
cloudaicompanion.googleapis.com prevents the Gemini CLI, Cloud Code, and Google Cloud console interfaces from connecting to the underlying LLM instances, completely disabling AI-assisted command generation.roles/editor at the organization level grants developers broad read/write access across all resources and projects in the entire enterprise hierarchy, violating the principle of least privilege.An organization wanted to completely prevent any developer from utilizing Gemini assistance in a sensitive project while granting unrestricted modification rights across all other services.
roles/cloudaicompanion.settingsAdmin role directly to individual developer user accounts, and configure Private Google Access without a VPC Service Controls perimeter.This approach grants developers the Gemini for Google Cloud Settings Admin (roles/cloudaicompanion.settingsAdmin) predefined role on an individual account basis and relies exclusively on Private Google Access for subnet-level routing to Google APIs.
roles/cloudaicompanion.settingsAdmin role grants full administrative permissions over Gemini settings, including the ability to configure metadata, prompt, and response logging settings in Cloud Logging. Developers only need prompt submission and code generation capabilities.A platform administrator needed full authority to manage enterprise-wide Gemini logging policies and configure setting bindings across projects.
cloudaicompanion.googleapis.com, add the API to a VPC Service Controls perimeter, and assign the roles/cloudaicompanion.user and roles/serviceusage.serviceUsageConsumer roles to an application developer Google Group.This architecture establishes secure, governed access to Gemini for Google Cloud assistance tools (such as Gemini in the CLI and IDE integrations) by leveraging native VPC Service Controls (VPC-SC) perimeters alongside least-privilege Identity and Access Management (IAM) group-based bindings.
cloudaicompanion.googleapis.com) to a VPC Service Controls service perimeter prevents data exfiltration by creating a strict security perimeter around the Google-managed AI backend.roles/cloudaicompanion.user provides the minimum permissions required for developers to interact with the LLM (e.g., cloudaicompanion.companions.generateChat and cloudaicompanion.companions.generateCode) while withholding administrative privileges such as roles/cloudaicompanion.settingsAdmin.roles/cloudaicompanion.user and roles/serviceusage.serviceUsageConsumer to a centralized Google Group aligns with best practices by avoiding individual role bindings and simplifying auditability.cloudaicompanion.googleapis.com service endpoint required to process CLI conversations and script synthesis.This solution directly satisfies enterprise governance requirements by securing data in transit and at the boundary using VPC-SC while enforcing principle-of-least-privilege access using dedicated predefined IAM roles applied to identity groups.
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