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 custom-mode VPC network (prod-vpc) connected to an on-premises data center via a Cloud Interconnect VLAN attachment and a Cloud Router. You need to deploy a Cloud Build private worker pool with the following requirements:
prod-vpc (10.10.0.0/20) and an on-premises package registry (10.50.10.0/24).Which configuration should you implement?
When you establish a Private Services Access (PSA) connection to servicenetworking.googleapis.com, Google Cloud creates a VPC Network Peering link (servicenetworking-googleapis-com) between your VPC network and the Google-managed service producer network. By default, this peering relationship only exchanges subnet routes belonging to prod-vpc.
10.50.10.0/24 learned by the Cloud Router.10.20.0.0/21 is advertised toward on-premises.--export-custom-routes) is explicitly enabled on the consumer side of the peering connection.prod-vpc itself rather than in a separate peered VPC, because VPC Network Peering is non-transitive.199.36.153.8/30 or 199.36.153.4/30), or enable VPC Service Controls on the peering connection to prevent misrouting.Build workers only needed to communicate with workloads inside prod-vpc subnets (10.10.0.0/20) and did not require access to on-premises networks reachable via dynamic or static custom routes.
This configuration selects 172.17.0.0/16 as the Private Services Access (PSA) allocated range, which provides a large /16 block (65,536 addresses) for the service producer network. However, Cloud Build explicitly reserves both 172.17.0.0/16 and 192.168.10.0/24 internally for its Docker bridge network inside build worker environments.
172.17.0.0/16 for local Docker bridge routing, assigning 172.17.0.0/16 to the PSA allocation creates overlapping IP ranges.172.17.0.0/16 can be captured by the local container bridge interface inside the worker VM rather than routed across the VPC peering connection, breaking connectivity.192.168.10.0/24 and 172.17.0.0/16 should be avoided not only for PSA allocations but also for VPC subnets, GKE control plane endpoints, and on-premises targets that Cloud Build builders must reach.10.128.0.0/9 is reserved for automatically created subnets and cannot be allocated for PSA.The allocated IP range were changed to a non-conflicting RFC 1918 block outside 172.17.0.0/16 and 192.168.10.0/24, such as 10.20.0.0/21.
This configuration attempts to establish Private Services Access (PSA) connectivity for a Cloud Build private worker pool while conserving IPv4 address space by reserving a /26 CIDR block (10.20.0.0/26, providing 64 addresses). It correctly includes custom route export and Cloud Router advertisements for hybrid connectivity, as well as --no-public-egress to disable external IP addresses.
/24 or lower (wider), such as /24, /22, /21, or /16./24 subnets from the allocated PSA range for regional deployments. A /26 allocation is too small to satisfy the minimum /24 unit requirement and causes allocation or pool provisioning failures./24 or shorter, the peeredNetworkIpRange field on the private pool configuration itself can specify a smaller subrange (higher prefix length) inside an existing valid allocation./21 or /16 block prevents IP exhaustion when multiple private pools or additional PSA-backed services (such as Cloud SQL or Filestore) share the connection.The VPC-level global internal IP allocation used a prefix length of /24 or shorter (such as 10.20.0.0/21), and /26 were only specified as a subrange in the private pool's peeredNetworkIpRange setting.
Cloud Build private pools run inside a Google-owned service producer VPC network. By configuring Private Services Access (PSA)—which consists of a reserved global internal IP range (--purpose=VPC_PEERING) paired with a VPC Network Peering connection to servicenetworking.googleapis.com—you establish private, internal-IP communication between the isolated build workers and resources reachable through prod-vpc.
--no-public-egress (equivalent to setting egressOption to NO_PUBLIC_EGRESS) removes public IP addresses from the worker pool, strictly isolating build execution from the public internet.servicenetworking-googleapis-com peering connection with --export-custom-routes propagates the dynamic BGP routes learned from Cloud Router into the service producer network. Simultaneously advertising 10.20.0.0/21 via Cloud Router custom route advertisements ensures on-premises routers have a return path back to the worker pool over Cloud Interconnect.10.20.0.0/21 satisfies the PSA requirement for a /24 or shorter prefix, avoids overlapping with 10.10.0.0/20 and 10.50.10.0/24, and avoids Cloud Build's internal Docker bridge ranges (192.168.10.0/24 and 172.17.0.0/16).prod-vpc ensures traffic travels across only one VPC peering hop (service producer to prod-vpc) and then over Cloud Interconnect, respecting VPC Network Peering's non-transitive routing model./21 block provides 2,048 IP addresses, supporting multiple worker pools or additional Google-managed services without allocation exhaustion.prod-vpc can filter traffic sourced from 10.20.0.0/21.Unlike configurations that use undersized prefixes (/26), omit --export-custom-routes, or collide with Docker bridge networks (172.17.0.0/16), this design establishes bidirectional routing across both VPC and hybrid links while maintaining strict private 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