Refer to the exhibit. The network operation team opened a trouble ticket stating that users connected to R2 and R4 cannot reach server 1. Some partial configuration and show commands are included in the ticket: R4#sh ip route 10.71.2.100 Routing entry for 10.71.2.0/24 Known via "eigrp 100", distance 90, metric 35840, type internal Redistributing via eigrp 100 Last update from 10.3.111.2 on FastEthernet1/1, 00:01:14 ago Routing Descriptor Blocks: 10.3.111.2, from 10.3.111.2, 00:01:14 ago, via FastEthernet1/1 R2#sh ip route 10.71.2.0 Routing entry for 10.71.2.0/24 Known via "eigrp 100", distance 90, metric 33280, type internal Redistributing via eigrp 100 Last update from 10.1.95.2 on FastEthernet0/0, 00:12:58 ago Routing Descriptor Blocks: 10.1.95.2, from 10.1.95.2, 00:12:58 ago, via FastEthernet0/0 R2#sh run | i route ip route 10.71.2.100 255.255.255.255 Null0 name SERVER1 R2#sh run | s eigrp router eigrp 100 network 10.1.95.0 0.0.0.3 network 10.2.2.2 0.0.0.0 network 10.3.111.0 0.0.0.3 network 10.23.32.0 0.0.0.255 R4#sh run | i route ip route 10.71.2.0 255.255.254.0 Null0 name SERVER1 R4#sh run | s eigrp router eigrp 100 network 10.3.111.0 0.0.0.3 network 10.4.4.0 0.0.0.0 network 10.29.89.0 0.0.0.3 network 10.60.0.0 0.0.0.255 distance 200 10.29.89.2 0.0.0.0 10 Which configuration resolves the issue? (Choose one answer)

• A. R4# router eigrp 100 distance 160 10.29.89.2 0.0.0.0 10 ! no ip route 10.71.2.0 255.255.254.0 Null0 name SERVER1
• B. R2# router eigrp 100 distance 90 10.1.95.2 0.0.0.0 10 ! no ip route 10.71.2.100 255.255.255.255 Null0 name SERVER1
• C. R4# router eigrp 100 no distance 200 10.29.89.2 0.0.0.0 10 ! no access-list 10 permit 10.71.2.0 0.0.0.255
• D. R2# router eigrp 100 distance 170 10.1.95.2 0.0.0.0 10 ! no ip route 10.71.2.100 255.255.255.255 Null0 name SERVER1

Correct Answer: D

Brave-Dump Clients Votes