Your organization has a hub and spoke architecture with VPC Network Peering, and hybrid connectivity is centralized at the hub. The Cloud Router in the hub VPC is advertising subnet routes, but the on

Question

Options

• ACreate custom routes at the Cloud Router in the spokes to advertise the subnets of the VPC
• BCreate custom routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.
• CCreate a BGP route policy at the Cloud Router, and ensure the subnets of the VPC spokes are
• DCreate custom learned routes at the Cloud Router in the hub to advertise the subnets of the VPC

• A
  13% (5)
• B
  3% (1)
• C
  79% (31)
• D
  5% (2)

Explanation

In a hub-and-spoke topology using VPC Network Peering, routes from spoke VPCs are not automatically exported into the hub's Cloud Router BGP sessions-VPC Peering does not provide transitive routing. To advertise spoke subnet routes to on-premises through the hub's Cloud Router, you must create a BGP route policy on the Cloud Router that explicitly includes the spoke subnet prefixes in its route advertisements. Option B refers to 'custom routes,' which are static routes and do not apply here. Option A creates routes in the spokes, which would not reach the hub's Cloud Router. Option D refers to 'custom learned routes,' which is not the correct mechanism for advertisement.

No community discussion yet for this question.