nerdexam
Cisco

300-410 · Question #30

R2 has a locally originated prefix 192.168.130.0/24 and has these configurations: ip prefix-list test seq 5 permit 192.168.130.0/24 ! route-map OUT permit10 match ip address prefix-list test set…

The correct answer is A. R1 sees 192.168.130.0/24 as two hops away instead of one AS hop away. Applying the set as-path prepend command in an outbound BGP route-map causes the router to advertise a prefix with a longer AS_PATH attribute, making the route appear less desirable to the receiving eBGP neighbor.

Layer 3 Technologies

Question

R2 has a locally originated prefix 192.168.130.0/24 and has these configurations: ip prefix-list test seq 5 permit 192.168.130.0/24 ! route-map OUT permit10 match ip address prefix-list test set as-path prepend 65000 What is the result when the route-map OUT command is applied toward an eBGP neighbor R1 (1.1.1.1) by using the neighbor 1.1.1.1 route-map OUT command?

Exhibit

300-410 question #30 exhibit

Options

  • AR1 sees 192.168.130.0/24 as two hops away instead of one AS hop away
  • BR1 does not forward traffic that is destined for 192.168.130.0/24
  • CNetwork 192.168.130.0/24 is not advertised in the R1 table
  • DR1 does not accept any route other than 192.168.130.0/24.

How the community answered

(41 responses)
  • A
    93% (38)
  • B
    2% (1)
  • C
    5% (2)

Why each option

Applying the `set as-path prepend` command in an outbound BGP route-map causes the router to advertise a prefix with a longer AS_PATH attribute, making the route appear less desirable to the receiving eBGP neighbor.

AR1 sees 192.168.130.0/24 as two hops away instead of one AS hop awayCorrect

The `set as-path prepend 65000` command modifies the AS_PATH attribute of the advertised route by adding AS 65000 to the beginning of the path. When R1 receives this route, BGP path selection prefers shorter AS_PATHs, so R1 will perceive 192.168.130.0/24 as being further away (e.g., two AS hops instead of one), making it less preferred compared to other potential paths.

BR1 does not forward traffic that is destined for 192.168.130.0/24

Prepending the AS-PATH influences BGP path selection preference by making the path less attractive, but it does not prevent R1 from forwarding traffic to the prefix if it's still the best available route.

CNetwork 192.168.130.0/24 is not advertised in the R1 table

The route-map explicitly permits the 192.168.130.0/24 prefix; prepending an AS does not filter or prevent its advertisement to R1.

DR1 does not accept any route other than 192.168.130.0/24.

The route-map is applied outbound on R2 for a specific prefix and does not affect R1's ability to accept other routes from R2 or any other BGP peer.

Concept tested: BGP AS-PATH prepending for traffic engineering

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16-5/bgp-xe-16-5-book/bgp-as-path-attr.html

Topics

#BGP#Route-map#AS-Path Prepending#BGP Path Selection

Community Discussion

No community discussion yet for this question.

Full 300-410 Practice