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 uses a Shared VPC architecture with a host project (vpc-host) and two service projects (frontend-svc and backend-svc). You need to deploy a regional external Application Load Balancer in the Standard Network Service Tier using cross-project service referencing:
vpc-host: The network team has already created the VPC network, the REGIONAL_MANAGED_PROXY proxy-only subnet, and firewall rules.frontend-svc: The load balancer operations team must create and manage the forwarding rule, target HTTPS proxy, and regional URL map.backend-svc: The application team owns the regional backend service and Compute Engine VM instance groups.Which IAM role assignment follows the principle of least privilege for the load balancer operations team?
roles/compute.securityAdmin and roles/compute.networkUser on frontend-svc, roles/compute.networkUser on vpc-host, and roles/compute.loadBalancerServiceUser on backend-svc.roles/compute.securityAdmin doesThe Compute Security Admin role (roles/compute.securityAdmin) is designed for security administrators who manage VPC firewall rules and SSL certificates. It focuses on security policy enforcement and TLS certificate lifecycle rather than load balancer traffic routing or frontend provisioning.
roles/compute.securityAdmin nor roles/compute.networkUser grants permissions to create, update, or delete forwarding rules, target HTTPS proxies, or regional URL maps in frontend-svc.roles/compute.securityAdmin grants full permissions to create, modify, and delete firewall rules and SSL certificates, directly violating the constraint that the load balancer team must not manage those resources.roles/compute.loadBalancerServiceUser at the backend-svc project level allows referencing all current and future backend services in that project rather than only the target regional backend service.networkUser scope: roles/compute.networkUser allows consuming existing subnets and networks but does not permit creating load balancer frontend components.The team were a security administration team tasked exclusively with maintaining firewall rules and provisioning SSL certificates in frontend-svc, rather than deploying the load balancer's forwarding rule, target proxy, and URL map.
Because HTTPS load balancing requires SSL certificates, administrators sometimes confuse roles/compute.securityAdmin with load balancer management. In least-privilege architectures, the security team uses roles/compute.securityAdmin to provision certificates, while the load balancer team uses roles/compute.loadBalancerAdmin to attach them to target HTTPS proxies.
roles/compute.loadBalancerAdmin on frontend-svc, roles/compute.networkUser on the vpc-host subnets, and roles/compute.loadBalancerServiceUser on the regional backend service in backend-svc.This configuration pairs three specialized, least-privilege IAM roles across the Shared VPC boundary: Compute Load Balancer Admin (roles/compute.loadBalancerAdmin), Compute Network User (roles/compute.networkUser), and Compute Load Balancer Services User (roles/compute.loadBalancerServiceUser). Each role maps strictly to the resources the load balancer operations team must create or reference across the three projects.
frontend-svc: roles/compute.loadBalancerAdmin grants permissions to create, modify, and delete forwarding rules (including Standard Tier regional EXTERNAL_MANAGED rules), target HTTPS proxies, and regional URL maps without granting rights to alter VPC networks, subnets, routes, firewall rules, or SSL certificates.vpc-host: roles/compute.networkUser scoped to the vpc-host subnets allows the team to attach the regional external Application Load Balancer to the Shared VPC network and its REGIONAL_MANAGED_PROXY proxy-only subnet without modifying host project networking.backend-svc: roles/compute.loadBalancerServiceUser granted on the specific regional backend service provides the compute.backendServices.use permission, allowing the URL map in frontend-svc to route traffic to backends in backend-svc.roles/compute.securityAdmin and VPC topology under the host network team.roles/compute.networkUser at the subnet level and roles/compute.loadBalancerServiceUser on the individual backend service prevents unintended access to other subnets or backend services.EXTERNAL_MANAGED in Standard or Premium Tier), which require Shared VPC proxy-only subnets and regional URL maps.Compared to roles/compute.networkAdmin or project-wide bindings, this combination enforces the principle of least privilege at both the project and resource levels while supporting cross-project Shared VPC load balancing.
roles/compute.loadBalancerAdmin on frontend-svc, roles/compute.networkAdmin on vpc-host, and roles/compute.loadBalancerAdmin on backend-svc.This assignment grants roles/compute.loadBalancerAdmin in both service projects and roles/compute.networkAdmin in the Shared VPC host project (vpc-host). While it provides sufficient permissions to deploy the load balancer, it drastically exceeds what is needed in both vpc-host and backend-svc.
vpc-host: Granting roles/compute.networkAdmin on the host project gives the load balancer operations team permission to create, modify, and delete VPC networks, subnets (including proxy-only subnets), routes, and firewall rules across the entire Shared VPC host project.backend-svc: Granting roles/compute.loadBalancerAdmin on backend-svc allows the frontend team to modify or delete the application team's regional backend services, health checks, and load balancers, rather than merely referencing a backend service.roles/compute.networkAdmin in a Shared VPC host project impacts all attached service projects because it controls shared subnets, routes, and firewall rules.compute.backendServices.use permission, not full loadBalancerAdmin control over the backend project.REGIONAL_MANAGED_PROXY subnet in vpc-host, consuming that subnet only requires roles/compute.networkUser.The operations team were also designated as the central host network administrator for vpc-host and owned the backend services inside backend-svc.
Note also that Global external proxy Network Load Balancers do not support Shared VPC at all, whereas regional and global external Application Load Balancers do. When Shared VPC is used with cross-project referencing, roles/compute.networkUser in the host project and roles/compute.loadBalancerServiceUser on the target backend service preserve strict project boundaries.
roles/compute.networkAdmin on frontend-svc, roles/compute.networkUser on the vpc-host subnets, and roles/compute.loadBalancerServiceUser on the regional backend service in backend-svc.roles/compute.networkAdmin doesThe Compute Network Admin role (roles/compute.networkAdmin) provides broad administrative permissions to create, modify, and delete Compute Engine networking resources. While it includes permissions to provision load balancer components, its operational scope extends far beyond load balancing to encompass core VPC infrastructure and security controls.
frontend-svc: Granting roles/compute.networkAdmin allows the load balancer operations team to create, alter, and delete VPC networks, subnets, routes, firewall rules, and SSL certificates within frontend-svc.roles/compute.loadBalancerServiceUser is separately required.The team in frontend-svc were also responsible for managing standalone VPC networks, subnets, routes, firewall rules, and SSL certificates in that project rather than being restricted strictly to load balancer provisioning.
Although many general deployment walkthroughs assign roles/compute.networkAdmin to simplify setup in standalone projects, enterprise Shared VPC architectures should narrow permissions to roles/compute.loadBalancerAdmin whenever load balancer operations are separated from core network and firewall administration.
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