nerdexam
Cisco

400-007 · Question #26

Refer to the exhibit. An engineer has been asked to redesign the traffic flow toward AS 111 coming from AS 500. Traffic destined to AS 111 network 91.7.0.0/16 should come in via AS 100, while…

The correct answer is A. Prepend AS path for the 91.7.0.0/16 network and set it for neighbor in AS 200. AS path prepending on advertisements sent to AS 200 makes the path to 91.7.0.0/16 via AS 200 artificially longer, causing AS 500 to prefer the shorter path through AS 100 for that specific prefix.

Designing Network Infrastructure

Question

Refer to the exhibit. An engineer has been asked to redesign the traffic flow toward AS 111 coming from AS 500. Traffic destined to AS 111 network 91.7.0.0/16 should come in via AS 100, while traffic destined to all other networks in AS 111 should continue to use the existing path. Which BGP attributes are best suited to control this inbound traffic coming from BGP AS 500 into the 91.7.0.0/16 network?

Exhibit

400-007 question #26 exhibit

Options

  • APrepend AS path for the 91.7.0.0/16 network and set it for neighbor in AS 200.
  • BUse extended community for the 91.7.0.0/16 network, not advertising it to the bi-lateral peer.
  • CUse local preference on R1 for the networks that AS 500 advertises to AS 111.
  • DSet higher MED for neighbor in AS 100 to influence incoming traffic for the 91.7.0.0/16 network.

How the community answered

(23 responses)
  • A
    43% (10)
  • B
    30% (7)
  • C
    17% (4)
  • D
    9% (2)

Why each option

AS path prepending on advertisements sent to AS 200 makes the path to 91.7.0.0/16 via AS 200 artificially longer, causing AS 500 to prefer the shorter path through AS 100 for that specific prefix.

APrepend AS path for the 91.7.0.0/16 network and set it for neighbor in AS 200.Correct

By prepending the AS path on the 91.7.0.0/16 advertisement sent to AS 200 (the unwanted inbound path), AS 111 makes that route appear less attractive to AS 500 due to a longer AS path length - since AS path length is evaluated before MED in the BGP decision process. AS 500 then selects the path through AS 100 for 91.7.0.0/16 while all other prefixes continue to use the existing path through AS 200 because they carry no additional prepends.

BUse extended community for the 91.7.0.0/16 network, not advertising it to the bi-lateral peer.

Not advertising 91.7.0.0/16 to the bilateral peer would make that network completely unreachable via that peer, which is not the goal - the goal is to influence which path inbound traffic uses, not to withdraw reachability.

CUse local preference on R1 for the networks that AS 500 advertises to AS 111.

Local preference is an internal BGP attribute used within a single AS to influence outbound path selection; it is not propagated to external BGP peers and cannot influence how AS 500 sends traffic toward AS 111.

DSet higher MED for neighbor in AS 100 to influence incoming traffic for the 91.7.0.0/16 network.

A higher MED advertised to AS 100 would signal to AS 100 that the path into AS 111 via that link is less preferred, which would discourage traffic from entering via AS 100 - the opposite of the desired behavior.

Concept tested: BGP AS path prepending for inbound traffic engineering

Source: https://www.cisco.com/c/en/us/support/docs/ip/border-gateway-protocol-bgp/13759-37.html

Topics

#BGP#AS path prepending#inbound traffic engineering#MED

Community Discussion

No community discussion yet for this question.

Full 400-007 Practice