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 is onboarding a new application team to a Shared VPC architecture. Both the host project (prod-host-vpc) and the service project (app-team-svc) reside in the Production folder. You must enforce strict separation of duties:
app-team-svc.prod-host-vpc, without modifying firewall rules or Shared VPC attachments.app-team-svc using only the app-subnet-1 subnet in prod-host-vpc, without access to other current or future subnets.Which combination of IAM role assignments satisfies these requirements?
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin on the Production folder to the Platform Networking Team; grant roles/compute.networkAdmin on prod-host-vpc to the Network Operations Team; grant roles/compute.networkUser on the app-subnet-1 subnet in prod-host-vpc, and roles/compute.instanceAdmin and roles/compute.networkUser on app-team-svc to the Application Team.Shared VPC uses Identity and Access Management (IAM) bindings across folder, host project, subnet, and service project boundaries to enforce the principle of least privilege. By splitting Shared VPC Admin, Network Admin, and Service Project Admin duties, an organization can centralize network governance while empowering application teams to deploy workloads independently.
roles/compute.xpnAdmin) and Project IAM Admin (roles/resourcemanager.projectIamAdmin) on the Production folder covers both prod-host-vpc and app-team-svc. This allows the team to enable host projects, attach service projects within the same folder hierarchy, and delegate subnet permissions without granting VM management rights in app-team-svc.roles/compute.networkAdmin) on prod-host-vpc grants full control over VPC networks, subnets, routes, and Cloud Routers, while withholding permissions to modify firewall rules, SSL certificates, or Shared VPC attachments.roles/compute.networkUser specifically on the app-subnet-1 resource in prod-host-vpc restricts the team to that single subnet and prevents access to other existing or future subnets. Pairing this with Compute Instance Admin (roles/compute.instanceAdmin) and roles/compute.networkUser on app-team-svc enables full VM lifecycle management inside the service project.roles/compute.networkUser bindings prevent service project teams from consuming unapproved IP ranges or regions.roles/compute.securityAdmin from Network Operations preserves a separate security boundary for firewall rules.roles/compute.xpnAdmin on the Production folder limits attachment authority to projects within that folder and its subfolders.app-team-svc while consuming centrally managed IP space.Unlike project-level host bindings or overly broad administrative roles, this combination assigns the exact minimum predefined roles at the lowest required resource hierarchy level for every team.
roles/compute.xpnAdmin on the Production folder to the Platform Networking Team; grant roles/compute.securityAdmin on prod-host-vpc to the Network Operations Team; grant roles/compute.networkUser on the app-subnet-1 subnet in prod-host-vpc, and roles/compute.instanceAdmin and roles/compute.networkUser on app-team-svc to the Application Team.This configuration correctly scopes subnet usage for the Application Team, but it assigns Compute Security Admin (roles/compute.securityAdmin) to the Network Operations Team and omits Project IAM Admin (roles/resourcemanager.projectIamAdmin) from the Platform Networking Team.
roles/compute.securityAdmin role manages firewall rules and SSL certificates, not VPCs, subnets, or Cloud Routers. Assigning it to Network Operations directly violates the requirement prohibiting firewall rule modifications while failing to grant permissions to create subnets or Cloud Routers.roles/compute.xpnAdmin enables host projects, attaches service projects, and modifies subnet IAM policies, omitting roles/resourcemanager.projectIamAdmin prevents the Platform Networking Team from managing project-level IAM bindings when delegating access to all existing and future subnets in a host project.roles/compute.networkAdmin controls routing, subnets, and VPCs (excluding firewalls and SSL certificates), whereas roles/compute.securityAdmin controls firewalls and SSL certificates exclusively.roles/compute.xpnAdmin with roles/resourcemanager.projectIamAdmin at the folder or organization level.The Network Operations Team were instead a Security Operations Team tasked strictly with managing firewall rules and SSL certificates in prod-host-vpc, and the Platform Networking Team also received roles/resourcemanager.projectIamAdmin.
Separating roles/compute.networkAdmin and roles/compute.securityAdmin is a core Google Cloud security best practice that prevents network engineers from unilaterally altering security firewall postures.
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin on prod-host-vpc to the Platform Networking Team; grant roles/compute.networkAdmin on prod-host-vpc to the Network Operations Team; grant roles/compute.networkAdmin on the app-subnet-1 subnet in prod-host-vpc, and roles/compute.instanceAdmin on app-team-svc to the Application Team.This option attempts to configure Shared VPC administration at the project level and uses Compute Network Admin (roles/compute.networkAdmin) instead of Compute Network User (roles/compute.networkUser) to grant the Application Team access to app-subnet-1.
roles/compute.xpnAdmin role cannot be granted at the project level; its lowest supported resource level is a folder or the organization. Without folder- or organization-level permissions spanning both prod-host-vpc and app-team-svc, the Platform Networking Team cannot attach service projects.roles/compute.networkAdmin does not make a principal a Service Project Admin. The roles/compute.networkUser role includes specific subnet consumption permissions (such as using subnets for VM creation) that are absent from roles/compute.networkAdmin.roles/compute.networkAdmin were applied at the host project level, it is intended for managing network infrastructure rather than consuming shared subnets.roles/compute.networkAdmin allows creating, modifying, and deleting networks and subnets, whereas roles/compute.networkUser grants permission to attach resources to existing Shared VPC subnets.roles/compute.xpnAdmin.roles/compute.networkUser alongside roles/compute.instanceAdmin in the service project to attach instances cleanly.No valid scenario makes this answer correct as written, because roles/compute.xpnAdmin requires folder or organization scope and roles/compute.networkUser is mandatory for Service Project Admins.
A common misconception is that roles/compute.networkAdmin is a strict superset of roles/compute.networkUser. In Google Cloud, their permission sets differ, so a Network Admin lacking roles/compute.networkUser cannot act as a Service Project Admin.
roles/compute.xpnAdmin and roles/resourcemanager.projectIamAdmin on the Production folder to the Platform Networking Team; grant roles/compute.networkAdmin on prod-host-vpc to the Network Operations Team; grant roles/compute.networkUser on prod-host-vpc, and roles/compute.instanceAdmin and roles/compute.networkUser on app-team-svc to the Application Team.This configuration correctly separates Shared VPC attachment administration and host-project network management, but it applies the Compute Network User (roles/compute.networkUser) role at the host project level (prod-host-vpc) instead of the individual subnet level.
roles/compute.networkUser on the entire prod-host-vpc project defines the Application Team as project-level Service Project Admins. This gives them permission to deploy resources into all VPC networks and subnets inside prod-host-vpc, including any subnets created in the future.app-subnet-1.roles/compute.networkUser at the host project level can list and consume all shared subnets from any attached service project.The Application Team oversaw multiple application tiers across the organization and required unrestricted access to all existing and future subnets in prod-host-vpc rather than being limited to app-subnet-1.
In a Shared VPC environment, project-level roles/compute.networkUser bindings are best reserved for centralized teams that oversee all environments, whereas subnet-level bindings enforce regional and workload isolation.
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