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 has connected a Google Cloud VPC network (vpc-prod) to an on-premises data center in the us-east1 region using Dedicated Interconnect VLAN attachments and a regional Cloud Router. Workloads in vpc-prod must initiate outbound HTTP connections to an on-premises patch server without re-addressing either network.
Network topology and constraints:
subnet-app in us-east1): 192.168.10.0/24192.168.10.0/24 (hosts local corporate workstations)192.168.20.0/24 (non-overlapping)10.10.1.0/29How should you deploy and configure Private NAT to enable this hybrid connectivity?
This approach correctly provisions a dedicated PRIVATE_NAT subnet (10.10.1.0/29), a PRIVATE Cloud NAT gateway on the regional Cloud Router, and the nexthop.is_hybrid match rule. However, it misconfigures the Border Gateway Protocol (BGP) route advertisements between Google Cloud and the on-premises router by exchanging the colliding 192.168.10.0/24 prefix while omitting the 10.10.1.0/29 NAT range.
10.10.1.0/29 Private NAT subnet range to the on-premises network, the on-premises patch server in 192.168.20.0/24 has no route back to the SNAT-translated source IP addresses, causing all response packets to be dropped.192.168.10.0/24 from Cloud Router causes an IP conflict with the existing 192.168.10.0/24 corporate workstation subnet on-premises. Similarly, advertising 192.168.10.0/24 from on-premises into vpc-prod introduces conflicting dynamic routes that collide with the local subnet-app subnet route.PRIVATE_NAT subnet CIDR (10.10.1.0/29) via BGP so external networks can route return traffic back to the Cloud NAT gateway.192.168.10.0/24 into a VPC, local VPC subnet routes take precedence over remote dynamic routes for overlapping ranges.Cloud Router advertised 10.10.1.0/29 instead of 192.168.10.0/24, and the on-premises router advertised only the non-overlapping 192.168.20.0/24 prefix.
A Public NAT gateway enables Google Cloud resources without external IP addresses (such as Compute Engine VMs or GKE nodes) to initiate outbound connections to destinations on the public internet using shared external IPv4 addresses. It is not designed for private-to-private translation across hybrid links.
10.10.1.0/29. Furthermore, Private NAT strictly requires a subnet created with --purpose=PRIVATE_NAT rather than a standard VM subnet.nexthop.is_hybrid match expression required to translate traffic bound for on-premises dynamic routes.PUBLIC or PRIVATE NAT, never both. Two separate gateways on the Cloud Router are needed if a subnet requires both internet egress and hybrid translation.0.0.0.0/0) or 0.0.0.0/1 over a VLAN attachment, Public NAT becomes inoperable for that destination because the next hop is no longer the default internet gateway.The workloads in subnet-app needed to download updates from a public internet repository using dedicated external static IP addresses rather than reaching an internal on-premises subnet over Dedicated Interconnect.
Hybrid NAT (a mode of Cloud Private NAT) performs private-to-private source network address translation (SNAT) and return destination network address translation (DNAT) between a Google Cloud VPC network and an on-premises or external cloud network connected via Cloud Interconnect or Cloud VPN. Unlike Public NAT, which translates traffic bound for the internet, Private NAT translates source IP addresses from a dedicated PRIVATE_NAT subnet so workloads in overlapping VPC ranges can communicate with non-overlapping external subnets.
--purpose=PRIVATE_NAT): Creating 10.10.1.0/29 in us-east1 with the PRIVATE_NAT purpose reserves an unallocated, non-overlapping pool of IPv4 addresses exclusively for translation. No VM instances or other resources can be deployed inside this subnet.type=PRIVATE Cloud NAT gateway on the us-east1 Cloud Router for subnet-app with a custom rule matching nexthop.is_hybrid instructs Google Cloud's Andromeda SDN stack to translate egress packets routed over hybrid dynamic routes.192.168.20.0/24 prefix (excluding 192.168.10.0/24) prevents BGP prefix collisions in vpc-prod. Advertising 10.10.1.0/29 from Cloud Router ensures the on-premises network has a valid return path for translated response packets.subnet-app (192.168.10.x) sends an HTTP packet destined for the patch server in 192.168.20.0/24.nexthop.is_hybrid rule triggers SNAT, rewriting the source IP and port to an allocated tuple within 10.10.1.0/29.10.10.1.0/29 address, routing back across the Dedicated Interconnect via the Cloud Router advertisement.192.168.10.x destination.This managed, software-defined approach requires zero proxy VMs, avoids re-IPing existing workloads, and eliminates asymmetric or broken routing caused by overlapping 192.168.10.0/24 prefixes.
Hybrid Subnets (allow-cidr-routes-overlap) is a VPC migration feature that allows a Google Cloud subnet and an on-premises network segment to temporarily share the same logical CIDR block during an incremental workload migration. When enabled, Google Cloud relaxes standard route overlap restrictions so traffic for unmatched local IP addresses can be forwarded over dynamic or static routes to the on-premises portion of that shared subnet.
192.168.10.0/24 is unique across both locations. In this scenario, 192.168.10.0/24 in Google Cloud and 192.168.10.0/24 on-premises are two independent subnets with colliding host IP addresses.192.168.10.x in vpc-prod to 192.168.20.x still carry a 192.168.10.x source IP. When the on-premises patch server attempts to reply to 192.168.10.x, the on-premises network routes the reply locally to the on-premises 192.168.10.0/24 workstation subnet instead of sending it back across Dedicated Interconnect./32 custom BGP route advertisements for each migrated VM.10.10.1.0/29 block to disambiguate colliding networks.You were incrementally migrating VMs from an on-premises 192.168.10.0/24 subnet into Google Cloud while preserving unique host IPs across a single shared CIDR block.
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