Answer-first summary for fast verification
Answer: Create a BGP route policy at the Cloud Router, and ensure the subnets of the VPC spokes are being announced towards the on-premises environment.
In a hub-and-spoke architecture with VPC Network Peering, the issue arises because the Cloud Router in the hub is not automatically advertising the subnet routes of the VPC spokes to the on-premises router. The correct solution involves creating a BGP route policy at the Cloud Router in the hub to ensure that the subnets of the VPC spokes are being announced towards the on-premises environment. This is because BGP is the protocol used to exchange routing information between the cloud and on-premises networks, and a route policy is necessary to control which routes are advertised. Options A and B suggest creating custom routes, which does not address the need for BGP advertisement. Option D mentions custom learned routes, which are not relevant for advertising local or peered subnets via BGP.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
Your organization uses a hub-and-spoke architecture with VPC Network Peering, where hybrid connectivity is centralized in the hub. The Cloud Router in the hub VPC advertises subnet routes, but the on-premises router is not receiving any subnet routes from the spoke VPCs. How should you troubleshoot and resolve this issue?
A
Create custom routes at the Cloud Router in the spokes to advertise the subnets of the VPC spokes.
B
Create custom routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.
C
Create a BGP route policy at the Cloud Router, and ensure the subnets of the VPC spokes are being announced towards the on-premises environment.
D
Create custom learned routes at the Cloud Router in the hub to advertise the subnets of the VPC spokes.