What will Router 2 do with the routes shown in the exhibit?

Refer to the Exhibit.

Router 2 is receiving a route to 10.0.0.0/8 from Router 4 and Router 5. What will Router 2 do with the routes shown in the exhibit?

A.
Router 2 will mark both routes active if the next hops are reachable.

B.
Router 2 will prefer the route received from Router 4 because of a lower origin code value.

C.
Router 2 will prefer the route that arrived first because neither route is necessarily preferable over the other.

D.
Router 2 will prefer the route received from Router 5 because it has a shorter AS path.

Explanation:
Now, lets look at AS-PATH prepending. AS-PATH prepending changes the way that your advertised prefixes appear to the rest of the Internet. The as-path length is evaluated early on in the path select process so this is a powerful tool to use with BGP. The shorter the AS-PATH the more preferred a prefix becomes. AS-PATH prepending is used to make a route less desirable, along a specific path, by making the AS-PATH longer

Before the router installs a BGP route, it must make sure that the BGP next-hop attribute is reachable. If the BGP next hop cannot be resolved, the route is not installed. When a BGP route is installed in the routing table, it must go through a path selection process if multiple routes exist to the same destination prefix. The BGP path selection process proceeds in the following order:

1. Route preference in the routing table is compared. For example, if an OSPF and a BGP route exist for a particular destination, the OSPF route is selected as the active route because the OSPF route has a default preference of 10, while the BGP route has a default preference of 170.
2. Routes are compared for local preference. The route with the highest local preference is preferred. For example, see Examine the Local Preference Selection.
3. The AS path attribute is evaluated. The shorter AS path is preferred.
4. The origin code is evaluated. The lowest origin code is preferred ( I (IGP) < E (EGP) < ? (Incomplete)).
5. The MED value is evaluated. By default, if any of the routes are advertised from the same neighboring AS, the lowest MED value is preferred. The absence of a MED value is interpreted as a MED of 0. For an example, see Examine the Multiple Exit Discriminator Route Selection.
6. The route is evaluated as to whether it is learned through EBGP or IBGP. EBGP learned routes are preferred to IBGP learned routes. For an example, see Examine the EBGP over IBGP Selection
7. If the route is learned from IBGP, the route with the lowest IGP cost is preferred. For an example, see Examine the IGP Cost Selection. The physical next hop to the IBGP peer is installed according to the following three rules:

* After BGP examines the inet.0 and inet.3 routing tables, the physical next hop of the route with the lowest preference is used.
*
* If the preference values in the inet.0 and the inet.3 routing tables are a tie, the physical next hop of the route in the inet.3 routing table is used.
*
* When a preference tie exists in the same routing table, the physical next hop of the route with more paths is installed.

8. The route reflection cluster list attribute is evaluated. The shortest length cluster list is preferred. Routes without a cluster list are considered to have a cluster list length of 0.
9. The router ID is evaluated. The route from the peer with the lowest router ID is preferred (usually the loopback address).
10. The peer address value is examined. The peer with the lowest peer IP address is preferred.

Useful link:
http://www.juniper.net/techpubs/en_US/junos10.0/information-products/topic-collections/nog-baseline/bgp-routes-and-selection-introduction.html