Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Developer practice bank has an additional 608 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your development team is preparing a new Google Cloud project to deploy cloud-native workloads using Infrastructure Manager and several Google Cloud APIs. A developer who currently holds only the Viewer (roles/viewer) role receives a permission error when running gcloud services enable.
To comply with organizational security governance, you must meet the following requirements:
Which IAM role should you grant to the developer, and what security implication occurs upon API activation?
roles/servicemanagement.serviceConsumer) role, and note that activating an API automatically elevates existing project viewers to administrators for that newly enabled service.The Service Consumer (roles/servicemanagement.serviceConsumer) role is a narrow role within the Service Management API that contains only the servicemanagement.services.bind permission. This permission allows a caller to view and enable a specific producer-managed service on projects they control.
config.googleapis.com or iam.googleapis.com) require the serviceusage.services.enable permission provided by roles/serviceusage.serviceUsageAdmin, not just servicemanagement.services.bind.roles/viewer) principals to administrators. Principals with roles/viewer continue to receive only read-only permissions (such as roles/config.viewer for Infra Manager), while Google Cloud provisions a dedicated service agent for the service itself.servicemanagement.services.bind.gcloud services enable.A service account or user only needed to see and bind a specific Service Management-backed managed service (like Managed Service for Microsoft Active Directory) to a project they already control.
Enabling a service activates its control plane and provisions its Google-managed service agent, but it never automatically upgrades human users from read-only roles to administrative roles. Access for users remains strictly governed by IAM allow policies.
roles/serviceusage.serviceUsageAdmin) role, and note that activating an API automatically creates a Google-managed service account (service agent) in the project with permissions on project resources.The Service Usage Admin (roles/serviceusage.serviceUsageAdmin) role is a predefined Identity and Access Management (IAM) role dedicated to managing the lifecycle of Google Cloud APIs and services within a project. It includes the serviceusage.services.enable permission required to activate and deactivate APIs without granting administrative control over the underlying cloud resources. Meanwhile, a service agent is a Google-managed service account that Google Cloud automatically provisions when certain APIs are activated so the service can act on project resources.
roles/serviceusage.serviceUsageAdmin provides the exact serviceusage.services.enable and service management permissions needed to run gcloud services enable, avoiding overly broad basic roles.roles/cloudconfig.serviceAgent) to it. This grants the service agent permissions like iam.serviceAccounts.actAs, storage.buckets.*, and cloudbuild.builds.* across project resources.Compared to basic roles like Owner (roles/owner) or Editor (roles/editor), Service Usage Admin minimizes the blast radius of compromised developer credentials while accurately reflecting how Google Cloud provisions service agent identities during API activation.
roles/owner) role, and note that enabling APIs requires setIamPolicy permissions and transfers the caller's permissions to all newly created service resources.The Owner (roles/owner) role is a basic IAM role that provides full administrative control over all resources within a Google Cloud project. In addition to all permissions included in the Editor role, it grants setIamPolicy and getIamPolicy permissions, enabling a principal to modify access policies and take ownership of project data and services.
roles/owner includes serviceusage.services.enable, granting full project ownership to a developer solely to enable and disable APIs exposes the entire project to unnecessary risk, especially through unrestricted setIamPolicy permissions.setIamPolicy, nor does it transfer the caller's personal permissions to newly provisioned resources. Instead, Google Cloud provisions a dedicated Google-managed service agent with a predefined service agent role.setIamPolicy.A principal explicitly needed full administrative authority over the entire project, including billing linkages, project deletion, and managing IAM policies for all team members.
A common misconception is that because project creators automatically receive roles/owner and can enable APIs, Owner is required for service activation. In reality, Service Usage Admin (roles/serviceusage.serviceUsageAdmin) isolates API enablement without granting setIamPolicy.
roles/servicemanagement.admin) role, and note that activating an API only exposes REST endpoints without creating any new service identities or IAM bindings in the project.The Service Management Administrator (roles/servicemanagement.admin) role belongs to the Service Infrastructure / Service Management API (servicemanagement.googleapis.com). It is designed for service producers who create, configure, update, delete, and roll out managed services (such as Cloud Endpoints APIs) and manage service consumer policies and quotas.
roles/servicemanagement.admin includes serviceusage.services.get and serviceusage.quotas.get for inspecting service status, it does not include the serviceusage.services.enable permission required to enable or disable Google Cloud APIs on a consumer project.servicemanagement.services.create, update, delete, rollouts, and configs).servicemanagement.services.bind for binding managed services, rather than general Google Cloud API activation.serviceusage.services.get), causing gcloud services enable for standard Google Cloud APIs to fail.The developer needed to publish, update, configure, and manage IAM policies for a custom managed service built on Google Cloud Service Infrastructure rather than enabling Google Cloud APIs.
Students often confuse servicemanagement roles with serviceusage roles because both relate to services. Remember that Service Usage controls enabling and disabling Google Cloud APIs in a project, while Service Management governs custom producer-managed services.
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