Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Network Engineer practice bank has an additional 2,437 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization has a Shared VPC host project (host-vpc-prod) with subnets app-tier-us-west1 and db-tier-us-central1, and attached service projects svc-frontend and svc-database. Teams already hold roles/compute.instanceAdmin in their service projects. You must enforce these access controls:
frontend-devs and tf-deploy@svc-frontend.iam.gserviceaccount.com to app-tier-us-west1, blocking access to other regions or future subnets.dba-team to db-tier-us-central1.platform-leads to use all current and future subnets in host-vpc-prod without modifying VPC networks or firewall rules.Which IAM configuration should you implement?
roles/compute.networkUser at the host project level on host-vpc-prod to frontend-devs, tf-deploy@svc-frontend.iam.gserviceaccount.com, dba-team, and platform-leads, relying on service project attachments to isolate subnet access.Granting the Compute Network User (roles/compute.networkUser) role at the host project level designates the assigned principals as Service Project Admins for every Shared VPC network and subnet within that host project. While this provides broad connectivity for overarching administrators, it bypasses granular network segmentation across individual teams.
frontend-devs (along with its automation service account tf-deploy) and dba-team gain compute.subnetworks.use permission on both app-tier-us-west1 and db-tier-us-central1, allowing either team to deploy workloads into the other team's subnet.host-vpc-prod in the future, violating the requirement to block access to new subnets and additional regions.roles/compute.networkUser can deploy Compute Engine VMs, internal load balancers, and other eligible resources in any region where a subnet exists.This configuration would be appropriate if all teams (frontend-devs, dba-team, and platform-leads) shared responsibility across the entire environment and required unrestricted permission to deploy resources into every existing and future subnet across all regions in host-vpc-prod.
roles/compute.networkUser at the subnet level on app-tier-us-west1 to frontend-devs only, at the subnet level on db-tier-us-central1 to dba-team, and grant roles/compute.networkAdmin at the host project level on host-vpc-prod to platform-leads.This configuration fails in two critical ways: it leaves the Terraform automation service account (tf-deploy@svc-frontend.iam.gserviceaccount.com) unauthorized to consume the shared subnet, and it assigns the overly broad Compute Network Admin (roles/compute.networkAdmin) role to platform-leads instead of Compute Network User.
frontend-devs unless explicitly added or separately bound. Without roles/compute.networkUser on app-tier-us-west1, tf-deploy cannot attach new VMs or load balancers to the subnet.roles/compute.networkAdmin grants full permissions to create, modify, and delete VPC networks, subnets, routes, and VPNs in host-vpc-prod, directly violating the requirement that platform-leads must not modify VPC topologies.roles/compute.networkAdmin is designed for central network administrators managing infrastructure in the host project, not for Service Project Admins consuming subnets.roles/compute.networkUser allows principals to use existing host subnets to deploy resources without altering network configuration, whereas roles/compute.networkAdmin manages the lifecycle of networking resources themselves.roles/compute.networkUser bindings on the host project or target subnet.This configuration would only be valid if tf-deploy were a member of frontend-devs (or unused for provisioning into app-tier-us-west1) and platform-leads were central network administrators tasked with creating and modifying VPC networks and subnets in host-vpc-prod.
roles/compute.networkUser on svc-frontend to frontend-devs and tf-deploy@svc-frontend.iam.gserviceaccount.com, on svc-database to dba-team, and at the host project level on host-vpc-prod to platform-leads.Assigning roles/compute.networkUser on a service project (svc-frontend or svc-database) only grants permission to consume VPC networks and subnets defined locally inside that specific service project. It does not confer any authorization over networking resources owned by the Shared VPC host project (host-vpc-prod).
host-vpc-prod, so IAM authorization to attach VM NICs, internal load balancers, or GKE clusters to those subnets is evaluated against the host project and its individual subnet resources, not the service projects.frontend-devs, tf-deploy, and dba-team hold roles/compute.instanceAdmin in their service projects, attempts to create instances in app-tier-us-west1 or db-tier-us-central1 will fail with IAM permission errors because they lack compute.subnetworks.use on the host subnets.roles/compute.networkUser on service projects bypasses the host project's centralized subnet-level access controls.roles/compute.instanceAdmin) in the service project, paired with roles/compute.networkUser in the host project (or on specific host subnets).roles/compute.networkUser bindings only affect unshared, standalone VPC networks within that service project.Granting roles/compute.networkUser on svc-frontend or svc-database would only enable network consumption if the teams were deploying workloads into standalone VPC networks created inside their own service projects rather than consuming subnets from host-vpc-prod.
roles/compute.networkUser at the subnet level on app-tier-us-west1 to frontend-devs and tf-deploy@svc-frontend.iam.gserviceaccount.com, at the subnet level on db-tier-us-central1 to dba-team, and at the host project level on host-vpc-prod to platform-leads.This configuration combines granular subnet-level IAM bindings for workload-specific teams with a host-project-level IAM binding for cross-cutting platform oversight. By scoping the Compute Network User (roles/compute.networkUser) role directly to individual subnet resources or the host project depending on each principal's operational boundary, Shared VPC enforces strict least-privilege access.
roles/compute.networkUser directly on app-tier-us-west1 for both the frontend-devs Google group and the tf-deploy@svc-frontend.iam.gserviceaccount.com service account ensures human operators and CI/CD automation can deploy resources exclusively into that single subnet.frontend-devs and tf-deploy are blocked from deploying into db-tier-us-central1, other regions, or any subnets added to host-vpc-prod later.roles/compute.networkUser on db-tier-us-central1 for dba-team prevents database administrators from provisioning resources in app-tier-us-west1.roles/compute.networkUser at the host project level to platform-leads enables them to consume all current and future subnets across host-vpc-prod while denying permission to create, modify, or delete VPC networks, subnets, or firewall rules.compute.subnetworks.use permission required for its designated network segment.group:), individual users (user:), and user-managed service accounts (serviceAccount:).host-vpc-prod routing and firewalls.Unlike uniform project-level sharing (which over-privileges workload teams) or granting roles/compute.networkAdmin (which permits destructive network changes), combining subnet-level roles/compute.networkUser for tier teams with host-project-level roles/compute.networkUser for platform-leads satisfies every isolation, automation, and governance requirement simultaneously.
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