300-420 · Question #125
An engineer is upgrading a company's main site to include a connection to a second ISP. The company will receive full Internet routing tables from both ISPs via BGP. The engineer must ensure that…
The correct answer is A. Tag incoming routes from both ISPs with BGP community no-export. There are 4 methods how you can prevent becoming a transit AS: - Filter-list with AS PATH access-list. - No-Export Community. - Prefix-list Filtering - Distribute-list Filtering https://networklessons.com/bgp/bgp-prevent-transit-as
Question
An engineer is upgrading a company's main site to include a connection to a second ISP. The company will receive full Internet routing tables from both ISPs via BGP. The engineer must ensure that the company does not become a transit autonomous system. Which solution should be included in this design?
Options
- ATag incoming routes from both ISPs with BGP community no-export.
- BLower the MED for updates sent to the secondary ISP.
- CUse a route-map to prevent all prefixes from being advertised to either ISP.
- DModify the local-preference for routes incoming from the primary ISP.
How the community answered
(24 responses)- A75% (18)
- B17% (4)
- C4% (1)
- D4% (1)
Explanation
There are 4 methods how you can prevent becoming a transit AS: - Filter-list with AS PATH access-list. - No-Export Community. - Prefix-list Filtering - Distribute-list Filtering https://networklessons.com/bgp/bgp-prevent-transit-as
Topics
Community Discussion
No community discussion yet for this question.