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 Google Cloud organization has two separate folders: Network-Infra (with a new vpc-host-prod project) and App-Workloads (with an existing billing-app-prod project). You must implement Shared VPC with these requirements:
vpc-host-prod as a host project and attach billing-app-prod as a service project.billing-devs@example.com (who hold roles/compute.instanceAdmin.v1 in billing-app-prod) to deploy new VMs only in prod-app-subnet of vpc-host-prod, without modifying host project routes or firewall rules.Which configuration sequence meets all requirements?
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin to the network administrator on both the Network-Infra and App-Workloads folders, enable vpc-host-prod as a host project, attach billing-app-prod, and grant roles/compute.networkAdmin to billing-devs@example.com on vpc-host-prod.This approach properly satisfies the Shared VPC prerequisites and correctly scopes Shared VPC Admin permissions (roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin) across both Network-Infra and App-Workloads folders. However, instead of designating billing-devs@example.com as Service Project Admins with roles/compute.networkUser, it grants them the Compute Network Admin role (roles/compute.networkAdmin) on the vpc-host-prod host project.
vpc-host-prod except firewall rules and SSL certificates, meaning billing-devs@example.com could create, modify, or delete VPC routes, subnets, and VPC networks.roles/compute.networkAdmin on vpc-host-prod grants permissions across all VPC networks and subnets in the host project rather than restricting deployments solely to prod-app-subnet.roles/compute.networkAdmin) manages network infrastructure (subnets, routes, peering, VPNs), whereas Network User (roles/compute.networkUser) only grants permission to use shared subnets when deploying resources.roles/compute.networkAdmin explicitly excludes firewall rules and SSL certificates, which are managed by roles/compute.securityAdmin.roles/compute.networkAdmin on a host project allows service project developers to disrupt connectivity for all other attached service projects.billing-devs@example.com were members of the central network engineering team responsible for creating subnets and managing routing across vpc-host-prod, rather than an application team restricted to deploying VMs in a single subnet.
Confusing Network Admin (compute.networkAdmin) with Network User (compute.networkUser) is a frequent mistake in Shared VPC administration. Service Project Admins only need roles/compute.networkUser in the host project (ideally at the subnet level) to attach their service project VMs to a shared subnet.
roles/compute.xpnAdmin to the network administrator at the organization level, enable vpc-host-prod as a host project, attach billing-app-prod, and grant roles/compute.networkUser to billing-devs@example.com on the billing-app-prod project.This configuration assigns roles/compute.xpnAdmin at the organization root level without roles/resourcemanager.projectIamAdmin, and it binds roles/compute.networkUser for billing-devs@example.com on the service project (billing-app-prod) instead of on the target subnet inside the host project (vpc-host-prod).
roles/compute.xpnAdmin at the organization level violates the explicit constraint against granting organization-wide IAM roles to the network administrator.roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin so the administrator can also manage IAM bindings when delegating subnet access.roles/compute.networkUser on billing-app-prod only permits using networks defined inside billing-app-prod; it does not grant permission to use prod-app-subnet in vpc-host-prod.roles/compute.networkUser must be granted on the host project or directly on the specific host subnet resource.roles/resourcemanager.projectIamAdmin, an administrator with only roles/compute.xpnAdmin cannot complete the IAM delegation step to define Service Project Admins.billing-app-prod to vpc-host-prod only establishes a project-level link; it does not automatically grant billing-devs@example.com access to any host subnets.Organization-wide roles were permitted, roles/resourcemanager.projectIamAdmin were also included for the network administrator, and roles/compute.networkUser were bound to prod-app-subnet in vpc-host-prod rather than on billing-app-prod.
When onboarding an existing project like billing-app-prod, attaching it as a service project does not migrate its legacy VMs in the default VPC; new VMs must be created and explicitly pointed to the shared subnet in vpc-host-prod.
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin to the network administrator only on the Network-Infra folder, enable vpc-host-prod as a host project, attach billing-app-prod, and grant roles/compute.networkUser to billing-devs@example.com on the vpc-host-prod project.This configuration enables Shared VPC prerequisites (billing and the Compute Engine API) and grants Shared VPC Admin permissions (roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin) solely on the Network-Infra folder where the host project resides. It also assigns project-level Service Project Admin permissions by granting roles/compute.networkUser across the entire vpc-host-prod host project.
Network-Infra prevents the administrator from attaching billing-app-prod from the App-Workloads folder.roles/compute.networkUser at the host project level gives billing-devs@example.com access to all existing and future subnets in vpc-host-prod, failing the requirement to restrict VM deployments exclusively to prod-app-subnet.roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin on a single folder restricts attachment operations to projects inside that folder hierarchy.roles/compute.networkUser on the host project automatically exposes every subnet across all VPCs in that host project to the principal.Both vpc-host-prod and billing-app-prod were located inside the Network-Infra folder and the organization intended for billing-devs@example.com to deploy resources into any current or future subnet in the host project.
A common misconception is that Shared VPC Admin rights are only needed on the host project's parent resource. In reality, attaching a service project modifies the cross-project association of the service project as well, requiring Shared VPC Admin rights over both folders when projects are separated across folders.
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin to the network administrator on both the Network-Infra and App-Workloads folders, enable vpc-host-prod as a host project, attach billing-app-prod, and grant roles/compute.networkUser to billing-devs@example.com on prod-app-subnet.This configuration establishes a least-privilege Shared VPC architecture across two separate folders within a single Google Cloud organization. It satisfies every prerequisite, delegates Shared VPC Admin authority strictly to the required folders, links the host and service projects, and delegates subnet-level Service Project Admin permissions (roles/compute.networkUser) exclusively on prod-app-subnet.
compute.googleapis.com) on both projects satisfies the core service prerequisites. Granting roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin on both Network-Infra and App-Workloads gives the network administrator the Shared VPC Admin rights required across both folders to enable vpc-host-prod and attach billing-app-prod.roles/compute.networkUser specifically on prod-app-subnet makes billing-devs@example.com Service Project Admins for that single subnet. Combined with roles/compute.instanceAdmin.v1 in billing-app-prod, they can launch new VMs in prod-app-subnet while lacking permissions to alter routes, subnets, or firewall rules in vpc-host-prod.roles/compute.networkUser bindings restrict which regions and IP ranges a service project team can consume.billing-app-prod even though instances use vpc-host-prod networking.Unlike project-level roles/compute.networkUser or roles/compute.networkAdmin bindings on the host project, subnet-level Network User delegation paired with folder-scoped Shared VPC Admin permissions enforces exact least privilege at both the organizational hierarchy layer and the network consumption layer.
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