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 connects a Google Cloud VPC (vpc-prod) in us-central1 to an on-premises network via Cloud Interconnect and to other VPCs via a Network Connectivity Center (NCC) hub (corp-hub). vpc-prod contains two subnets:
subnet-overlap (10.10.0.0/24): Hosts 200 Compute Engine VMs and overlaps with an on-premises subnet.subnet-app (10.20.0.0/24): Non-overlapping subnet that must access Private Service Connect (PSC) propagated connections in corp-hub.You must configure Private NAT with static port allocation of 1,024 ports per VM so subnet-overlap VMs can reach non-overlapping destinations in corp-hub and on-premises without disrupting subnet-app PSC traffic.
Which configuration should you implement?
/29 PRIVATE_NAT subnet in us-central1 and advertise it over BGP from the Cloud Router without advertising 10.10.0.0/24. Create a Private NAT gateway with --nat-custom-subnet-ip-ranges=subnet-overlap:ALL, --no-enable-dynamic-port-allocation, and --min-ports-per-vm=1024, using a single rule matching nexthop.hub == "//networkconnectivity.googleapis.com/projects/PROJECT_ID/locations/global/hubs/corp-hub" || nexthop.is_hybrid mapped to the /29 subnet.This configuration correctly applies custom subnet mapping, static port allocation, Cloud Router BGP advertisement, and a combined next-hop NAT rule, but it provisions an undersized /29 PRIVATE_NAT subnet that cannot support 200 VMs at 1,024 static ports per VM.
2^(32 - 29) - 4 = 4 usable NAT IP addresses in a /29 subnet.1,024 minimum ports per VM, Cloud NAT actually reserves 2,048 ports per VM.64,512 usable TCP and UDP ports (ports 1,024 through 65,535). A /29 subnet supports at most floor((4 * 64,512) / (1,024 * 2)) = 126 VMs, leaving 74 VMs in subnet-overlap unable to obtain NAT port allocations.PRIVATE_NAT subnet is created, its CIDR prefix length cannot be increased or decreased.PRIVATE_NAT subnet cannot be resized in place, additional PRIVATE_NAT subnets can be attached to the gateway.subnet-overlap contained 126 or fewer VMs, or the PRIVATE_NAT subnet were sized as a /28 (12 usable IPs, supporting up to 378 VMs) instead of a /29./28 PRIVATE_NAT subnet in us-central1 and advertise it over BGP from the Cloud Router without advertising 10.10.0.0/24. Create a Private NAT gateway with --nat-all-subnet-ip-ranges, --no-enable-dynamic-port-allocation, and --min-ports-per-vm=1024, using a single rule matching nexthop.hub == "//networkconnectivity.googleapis.com/projects/PROJECT_ID/locations/global/hubs/corp-hub" || nexthop.is_hybrid mapped to the /28 subnet.This configuration properly sizes the PRIVATE_NAT subnet as a /28, enforces static port allocation, configures BGP route advertisement correctly, and combines the next-hop match conditions, but it enables Private NAT across all subnets in the region using --nat-all-subnet-ip-ranges.
--nat-all-subnet-ip-ranges, the Private NAT gateway is applied to subnet-app (10.20.0.0/24) in addition to subnet-overlap, breaking subnet-app's ability to reach PSC propagated services in corp-hub.--nat-custom-subnet-ip-ranges.subnet-app did not require connectivity to Private Service Connect propagated connections, or if --nat-all-subnet-ip-ranges were replaced with --nat-custom-subnet-ip-ranges=subnet-overlap:ALL./28 PRIVATE_NAT subnet in us-central1 and advertise it over BGP from the Cloud Router without advertising 10.10.0.0/24. Create a Private NAT gateway with --nat-custom-subnet-ip-ranges=subnet-overlap:ALL and --min-ports-per-vm=1024, then add Rule 100 matching nexthop.hub == "//networkconnectivity.googleapis.com/projects/PROJECT_ID/locations/global/hubs/corp-hub" and Rule 200 matching nexthop.is_hybrid, both mapped to the /28 subnet.This approach attempts to separate NCC Private NAT and Hybrid NAT into two distinct NAT rules on the same Private NAT gateway while omitting the flag required to switch from dynamic to static port allocation.
nexthop.hub and Rule 200 for nexthop.is_hybrid on the same gateway is rejected because the next-hop expressions differ.PRIVATE_NAT subnets must not overlap across NAT rules on the same gateway, making it invalid to assign the same /28 subnet to both Rule 100 and Rule 200.--no-enable-dynamic-port-allocation leaves dynamic port allocation enabled instead of enforcing fixed static port allocation.|| operator (nexthop.hub == "..." || nexthop.is_hybrid) when sharing a gateway.--min-ports-per-vm=1024 without disabling dynamic port allocation sets only the lower bound, allowing VMs to scale ports dynamically up to 65,536.--no-enable-dynamic-port-allocation were added for static allocation, and Rules 100 and 200 were consolidated into a single NAT rule with nexthop.hub == "..." || nexthop.is_hybrid./28 PRIVATE_NAT subnet in us-central1 and advertise it over BGP from the Cloud Router without advertising 10.10.0.0/24. Create a Private NAT gateway with --nat-custom-subnet-ip-ranges=subnet-overlap:ALL, --no-enable-dynamic-port-allocation, and --min-ports-per-vm=1024, using a single rule matching nexthop.hub == "//networkconnectivity.googleapis.com/projects/PROJECT_ID/locations/global/hubs/corp-hub" || nexthop.is_hybrid mapped to the /28 subnet.Private NAT (--type=PRIVATE) provides private-to-private source network address translation (SNAT) using regional internal IPv4 addresses from a dedicated PRIVATE_NAT subnet, enabling VMs in overlapping subnets to communicate with non-overlapping destinations across Network Connectivity Center (NCC) spokes and Cloud Interconnect hybrid links.
/28): Subtracting the 4 unusable addresses per IPv4 subnet, a /28 provides 2^(32 - 28) - 4 = 12 usable NAT IPs. Because Private NAT reserves twice the minimum ports per VM (1,024 * 2 = 2,048 ports) for reliability, a /28 supports floor((12 * 64,512) / 2,048) = 378 VMs, comfortably accommodating 200 VMs.--nat-custom-subnet-ip-ranges=subnet-overlap:ALL limits Private NAT strictly to subnet-overlap, preventing traffic from subnet-app to PSC propagated connections from being dropped.--no-enable-dynamic-port-allocation with --min-ports-per-vm=1024 explicitly enforces static allocation of 1,024 ports per VM.nexthop.hub == "..." || nexthop.is_hybrid enables both NCC spoke NAT and Hybrid NAT without violating the single-next-hop constraint across rules. Advertising only the non-overlapping /28 PRIVATE_NAT range over BGP (while suppressing 10.10.0.0/24) ensures symmetric return routing from on-premises.subnet-overlap seamlessly.PRIVATE_NAT subnets can be attached per gateway if future growth exceeds 378 VMs.This configuration satisfies exact port-reservation math, protects non-overlapping PSC propagation paths, adheres to Private NAT rule-consistency constraints, and enforces clean BGP route advertisement for hybrid return traffic.
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