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 organization is establishing a centralized network topology in Google Cloud to support multiple autonomous application teams while enforcing strict security and environment boundaries. You have designated a central host project (net-host-prod) containing a Shared VPC network with two distinct subnets: team-a-subnet and team-b-subnet.
You have created two dedicated service projects: service-team-a for Team A and service-team-b for Team B. You need to configure IAM roles and subnet access to satisfy the following requirements:
team-a-subnet.team-b-subnet.How should you configure the IAM role assignments across the host and service projects?
roles/compute.securityAdmin) role on the host project. In each service project, grant Team A and Team B the Compute Network Admin (roles/compute.networkAdmin) role. Attach the service projects to the host project using VPC Network Peering.This option attempts to delegate network administration by assigning roles/compute.networkAdmin in the service projects while using Compute Security Admin (roles/compute.securityAdmin) in the host project and connecting them via VPC Network Peering.
roles/compute.securityAdmin only permits managing firewall rules and SSL certificates; it does not grant full administrative control over VPC networks, subnets, and routes to the Network Engineering team.roles/compute.networkAdmin in the service projects gives development teams permission to manage local network objects and load balancing components, but does not provide access to host network subnets.net-host-prod as a host project). VPC Network Peering connects distinct standalone VPCs across projects rather than creating a centralized host/service project topology.The organization required decentralized, autonomous VPCs with direct non-transitive peering between distinct VPC networks instead of a centralized Shared VPC model.
roles/compute.networkAdmin) role on the host project. In the host project, grant Team A principals and the service-team-a Google APIs service account the Compute Network User (roles/compute.networkUser) role specifically on team-a-subnet, and grant Team B principals and the service-team-b Google APIs service account roles/compute.networkUser specifically on team-b-subnet. Grant each team Instance Admin (roles/compute.instanceAdmin.v1) within their respective service project.This architecture establishes a Shared VPC design where a single central host project manages underlying network topology and routing, while separate service projects host workloads managed by decentralized application teams. Subnet-level IAM access binding provides granular network segregation across service projects.
roles/compute.networkAdmin exclusively to the central team on the host project (net-host-prod) guarantees that only network engineers can modify network routes, subnets, and global configurations.roles/compute.networkUser) role directly to individual subnets (team-a-subnet and team-b-subnet) ensures that each team can only attach network interfaces to their authorized IP range. Team A cannot provision resources into Team B's subnet.roles/compute.instanceAdmin.v1 inside the respective service projects allows developers to manage virtual machines and templates. Binding roles/compute.networkUser on the subnet to the service project's Google APIs service account (SERVICE_PROJECT_NUM@cloudservices.gserviceaccount.com) is a mandatory requirement for automated instance provisioning in Managed Instance Groups (MIGs).Subnet-level IAM role delegation is the Google-recommended best practice for multi-tenant and multi-environment Shared VPC deployments. It separates administrative duties while strictly constraining resource placement across service projects.
roles/compute.networkAdmin) role on the host project. In the host project, create a custom IAM role containing only compute.subnetworks.use and grant it to both teams at the host project level. In each service project, grant the Compute Engine default service account the Owner (roles/owner) role.This configuration creates a custom IAM role at the host project level for developers and grants the broad Owner (roles/owner) role to the Compute Engine default service account in each service project.
roles/owner to default service accounts introduces severe security vulnerabilities by providing unrestricted access to project resources and IAM configurations.@cloudservices.gserviceaccount.com)—not just the Compute Engine default service account—requires the roles/compute.networkUser role on the specific host subnet to instantiate instances.roles/compute.networkUser is already tailored with the exact permissions (compute.subnetworks.use, compute.subnetworks.useExternalIp, compute.instances.use) needed for network attachment.The organization had a policy prohibiting standard predefined roles and operated all workloads inside a single homogeneous project perimeter without tenant isolation.
roles/compute.networkAdmin) role on the host project. In the host project, grant both Team A and Team B principals the Compute Network User (roles/compute.networkUser) role at the host project level. Grant each team Instance Admin (roles/compute.instanceAdmin.v1) within their respective service project.This configuration grants the Compute Network User (roles/compute.networkUser) role at the project level on the host project rather than on individual subnets.
roles/compute.networkUser at the host project level gives principals permission to use all current and future subnets across all VPC networks in the host project.team-b-subnet, directly violating the operational boundary and security requirement.compute.networkUser bindings apply globally to all subnets in the project.All application teams belonged to a single trusted domain where any engineer was permitted to attach workloads to any subnet within the Shared VPC without boundary restrictions.
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