nerdexam
Google

PROFESSIONAL-CLOUD-NETWORK-ENGINEER · Question #151

You are designing a hub-and-spoke network architecture for your company's cloud-based environment. You need to make sure that all spokes are peered with the hub. The spokes must use the hub's virtual

The correct answer is B. Create a default route in the hub VPC that points to IP address 10.0.0.5.. To enable spokes to use the hub's virtual appliance (Internal Load Balancer at 10.0.0.5) for internet access through VPC Network Peering, a default route must be established in the hub VPC.

Submitted by hassan_iq· Apr 18, 2026Designing, planning, and prototyping a Google Cloud network

Question

You are designing a hub-and-spoke network architecture for your company's cloud-based environment. You need to make sure that all spokes are peered with the hub. The spokes must use the hub's virtual appliance for internet access. The virtual appliance is configured in high-availability mode with two instances using an internal load balancer with IP address 10.0.0.5. What should you do?

Options

  • ACreate a default route in the hub VPC that points to IP address 10.0.0.5.
  • BCreate a default route in the hub VPC that points to IP address 10.0.0.5.
  • CCreate two default routes in the hub VPC that point to the next hop instances of the virtual
  • DCreate a default route in the hub VPC that points to IP address 10.0.0.5.

How the community answered

(67 responses)
  • A
    4% (3)
  • B
    70% (47)
  • C
    18% (12)
  • D
    7% (5)

Why each option

To enable spokes to use the hub's virtual appliance (Internal Load Balancer at 10.0.0.5) for internet access through VPC Network Peering, a default route must be established in the hub VPC.

ACreate a default route in the hub VPC that points to IP address 10.0.0.5.

This is identical to option B and indicates a potential question error, but B is marked correct.

BCreate a default route in the hub VPC that points to IP address 10.0.0.5.Correct

Creating a default route in the hub VPC that points to the internal load balancer's IP (10.0.0.5) establishes the virtual appliance as the next hop for internet-bound traffic originating in or routed through the hub VPC. When VPC Network Peering is configured to exchange custom routes, spokes can then direct their internet-bound traffic through the peered hub network to this appliance.

CCreate two default routes in the hub VPC that point to the next hop instances of the virtual

You do not create separate default routes for individual instances behind an Internal Load Balancer; the ILB's single IP address acts as the next hop, distributing traffic to its backend instances.

DCreate a default route in the hub VPC that points to IP address 10.0.0.5.

This is identical to option B and indicates a potential question error, but B is marked correct.

Concept tested: VPC peering and custom route exchange with internal load balancer

Source: https://cloud.google.com/vpc/docs/using-vpc-peering#custom_routes

Topics

#VPC Routing#Hub-and-Spoke#Internal Load Balancer#Network Virtual Appliance

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice