You have a global corporate network with 153 individual IP prefixes in your internal routing table. You establish a private virtual interface over AWS Direct Connect to a VPC that has an Internet gateway (IGW). All instances in the VPC must be able to route to the Internet via an IGW and route to the global corporate network via the VGW.
How should you configure your on-premises BGP peer to meet these requirements?
A. Configure AS-Prepending on your BGP session
B. Summarize your prefix announcement to less than 100
C. Announce a default route to the VPC over the BGP session
D. Enable route propagation on the VPC route table
answer is b.
In fact, you need to enable route propagation on the VPC route table. But the questions asks what should you configure on your on-premises BGP peer.
The question does not state that the BGP went down so i order for the routes to be available in the subnet’s route table route propagation needs to be enabled.
I agree, answer should be B. 100 prefix is the limit on BGP over direct connect.
https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html
I dont think answer is correct. You cannot advertise more than 100 routes on BGP or it will simply stop working.
Answer should be B to limit to 100 then advertise.