Refer to the exhibit. The routing tables of FortiGate_A and FortiGate_B are shown. FortiGate_A and FortiGate_B are in the same autonomous system. The administrator wants to dynamically add only…

Question

Exhibit

Options

• AThe prefix 172.16.1.248/30 in the BGP Networks section on FortiGate_B
• BA BGP route map out for 172.16.1.248/30 on FortiGate_B
• CEnable Redistribute Connected in the BGP section on FortiGate_B.
• DA BGP route map in for 172.16.1.248/30 on FortiGate_A

• A
  17% (11)
• B
  71% (47)
• C
  8% (5)
• D
  5% (3)

Explanation

FortiGate_A and FortiGate_B are in the same autonomous system (AS), and FortiGate_A does not currently have route 172.16.1.248/30 in its routing table. However, FortiGate_B has this route as a connected route. To dynamically advertise only 172.16.1.248/30 from FortiGate_B to FortiGate_A, the administrator must configure a BGP route map out on FortiGate_B that specifically permits only A BGP route map out on FortiGate_B controls which routes FortiGate_B advertises to FortiGate_A. If no filtering is applied, FortiGate_B might advertise all BGP-learned and connected routes, which is not what the administrator wants. The route map should include a prefix-list that explicitly allows only 172.16.1.248/30 and denies everything else.

No community discussion yet for this question.