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 deploying workloads for two application teams (dept-a and dept-b) using a centralized network model. Physical Dedicated Interconnect connections already exist in an interconnect-infra project in us-east1. You must satisfy these requirements:
dept-a-svc in us-east1 and dept-b-svc in us-west1) using only its assigned regional subnet.us-east1.Which configuration should you implement?
network-host project as the Shared VPC host project with regional dynamic routing mode, and attach dept-a-svc and dept-b-svc as service projects. Grant both teams roles/compute.networkUser at the network-host project level, and have the dept-b team create a Cloud Router and VLAN attachments in dept-b-svc in us-west1 referencing interconnect-infra.This configuration establishes network-host as a Shared VPC host project with regional dynamic routing, grants broad project-level subnet access to both teams, and delegates Cloud Router and VLAN attachment creation to the dept-b-svc service project.
dept-b-svc) does not connect it to the Shared VPC network in network-host, and Service Project Admins are not permitted or expected to manage hybrid attachments for shared networks.roles/compute.networkUser at the host project level gives both dept-a and dept-b teams permission to deploy resources into all subnets across all regions of network-host, allowing dept-a to launch VMs in us-west1 and vice versa.us-west1 contradicts the requirement to route both regions through a single pair of VLAN attachments in us-east1.us-east1 Cloud Router cannot advertise us-west1 subnets or propagate on-premises routes to us-west1 VMs.roles/compute.networkUser directly to individual subnet resources rather than the entire host project.The VPC used global dynamic routing, roles/compute.networkUser was scoped to individual subnets, and the single pair of us-east1 VLAN attachments and Cloud Router were created exclusively in network-host.
network-host project as the Shared VPC host project with global dynamic routing mode, and attach dept-a-svc and dept-b-svc as service projects. Grant each team the roles/compute.networkUser role only on its assigned subnet in network-host, and create the Cloud Router and VLAN attachments in network-host referencing the physical connections in interconnect-infra.This architecture combines Shared VPC centralized governance with cross-project Dedicated Interconnect attachment provisioning and global dynamic routing. A dedicated network-host project owns the Shared VPC network, subnets, firewall rules, Cloud Router, and VLAN attachments, while physical Interconnect ports remain isolated in interconnect-infra within the same Google Cloud organization.
roles/compute.networkUser at the subnet level rather than the host project level enforces least privilege. Because subnets are regional resources, dept-a can only instantiate VMs in the us-east1 subnet and dept-b can only deploy in the us-west1 subnet.roles/compute.networkAdmin or roles/compute.securityAdmin on network-host. As Service Project Admins in their respective projects, they manage compute workloads while central network administrators retain exclusive control over routes, firewalls, and hybrid links.network-host binds hybrid connectivity directly to the Shared VPC. Enabling global dynamic routing mode allows the us-east1 Cloud Router to advertise both the us-east1 and us-west1 subnets to on-premises BGP peers and propagate learned on-premises prefixes to VMs in both regions.interconnect-infra separates physical hardware billing and operations from VPC-level logical attachments.network-host apply uniformly across both service projects.network-host.Compared to VPC Network Peering or deploying attachments in service projects, hosting VLAN attachments directly in the Shared VPC host project with global dynamic routing and subnet-level IAM is simpler to scale, avoids peering route-exchange complexity, and preserves strict separation of duties.
network-host project as the Shared VPC host project with global dynamic routing mode, and attach dept-a-svc and dept-b-svc as service projects. Grant both teams roles/compute.networkAdmin on network-host, create the Cloud Router and VLAN attachments in interconnect-infra, and connect interconnect-infra to network-host using VPC Network Peering with default route exchange settings.This design configures network-host as a Shared VPC host project with global dynamic routing, grants the Network Admin (roles/compute.networkAdmin) role on the host project to both application teams, places VLAN attachments in interconnect-infra, and connects the two networks via VPC Network Peering using default settings.
roles/compute.networkAdmin on network-host gives both application teams full control over all network resources in the host project, including creating or deleting subnets, modifying VPC routes, and altering hybrid attachments. It also allows either team to deploy workloads into any subnet across any region.interconnect-infra and using VPC Network Peering with default settings prevents on-premises connectivity. By default, VPC Network Peering exchanges only subnet routes and does not export or import custom dynamic routes learned via BGP. Without explicitly enabling custom route export on interconnect-infra and custom route import on network-host, VMs in network-host receive no routes to on-premises prefixes.roles/compute.networkAdmin applies to every VPC network and networking component inside the host project.interconnect-infra will not automatically advertise peered Shared VPC subnets unless custom route advertisements are explicitly configured.Application teams received subnet-level roles/compute.networkUser instead of roles/compute.networkAdmin, and the VLAN attachments and Cloud Router were created directly in network-host rather than peered from interconnect-infra.
interconnect-infra as a Shared VPC host project and attach network-host as a service project, then configure network-host as a host project for dept-a-svc and dept-b-svc with regional dynamic routing mode. Grant each team the roles/compute.networkUser role only on its assigned subnet in network-host.This option attempts to chain Shared VPC relationships by making interconnect-infra a parent host project above network-host, while simultaneously using network-host as a host project for the application service projects and relying on regional dynamic routing.
network-host is attached to interconnect-infra as a service project, it cannot act as a host project for dept-a-svc and dept-b-svc. Additionally, a service project can attach to only a single host project.us-east1). Consequently, the us-west1 subnet in dept-b-svc would not be advertised to on-premises routers, and VMs in us-west1 would not receive learned on-premises routes.interconnect-infra) within the same organization without requiring interconnect-infra to become a Shared VPC host project.Instead of chaining Shared VPC projects, interconnect-infra remained a standalone infrastructure project holding only the physical ports, network-host served as the sole Shared VPC host project with global dynamic routing enabled, and the VLAN attachments and Cloud Router were provisioned directly in network-host.
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