Refer to the exhibit. Routing protocols are mutually redistributed on R3 and R1. Users report intermittent connectivity to services hosted on the 10.1.1.0/24 prefix.
Significant routing update changes are noticed on R3 when the show ip route profile command is run.
How must the services be stabilized?
The issue is due to a routing loop caused by the current administrative distance settings. R3 is learning about the 10.1.1.0/24 network through multiple paths: via iBGP from R4 with an administrative distance (AD) of 200, and via OSPF from R1 with an AD of 110. Since lower AD values are preferred, R3 chooses the OSPF path, which results in a routing loop. By reducing the administrative distance of iBGP from 200 to a value lower than 110 on R3, the path via iBGP from R4 will be preferred, thus resolving the routing loop and stabilizing the network.
B is correct After redistribution, R3 learns about network 10.1.1.0/24 via two paths:+ Internal BGP (IBGP): advertised from R4 with AD of 200 (and metric of 0)+ OSPF: advertised from R1 with AD of 110 (O E2) (and metric of 20)Therefore R3 will choose the path with the lower AD via OSPF But this is a looped path which is received from R3 -> R2 -> R1 -> R3. So when the advertised route from R4 is expired, the looped path is also expired soon and R3 willreinstall the main path from R4. This is the cause of intermittent connectivity.In order to solve this issue, we can lower the AD of iBGP to a value which is lower than 110 so that it is preferred over OSPF-advertised route.
Routing protocols are mutually redistributed on R3 and R1. R3 learns about network 10.1.1.0/24 via three paths: OSPF(110[O E2]), EIGRP(170[D EX]), iBGP(200). The IBGP has too much administrative distance. Packets with a destination address from the 10.1.1.0/24 subnet miss this path and travel in a circle. C and D are too strange options. Reducing the administrative distance makes the routes of this protocol more preferable. 10.1.1.0/24 is behind the BGP, hence option B.
B should be correct, C is general and we have more specific options. D would be correct if they mentioned public AS/IP, but u can see private on the exhibit
B is correct
B is correct
This is one lazy looking diagram.