7.

The list of decision steps BGP goes through is:

a. b. c. d. e. f. g. h. i. j.

Largest WEIGHT Largest LOCAL_PREF Locally originated path Shortest AS_PATH Lowest origin type Lowest Multi-Exit Discriminator (MED) External (eBGP) over internal (iBGP) path Lowest IGP metric over the BGP next hop. Multipath Determination. BGP router to prefer a current best path, if it has one, over a newer route with equal attributes

8. If your AS passes traffic from another AS to a third AS, BGP should not advertise a route before all routers in your AS learn about the route via IGP. BGP waits until IGP propagates the route within the AS and then advertises it to external peers. A BGP router with synchronization enabled does not install iBGP learned routes into its routing table if it is not able to validate those routes in its IGP. Issue the no synchronization command under router bgp in order to disable synchronization. This prevents BGP from validating iBGP routes in IGP. Refer to BGP Case Studies: Synchronization for a more detailed explanation. 9. IBGP is formed between Neighbors within the same AS whereas EBGP is formed between neighbors in different AS. A route learnt from an IBGP peer will not be advertised back to another IBGP by default. AS path is not prepended to the route when advertised to an IBGP peer. Attributes like local preference are sent to the IBGP peers but not to an EBGP peer. Under normal circumstances EBGP route is always preferred over an IBGP route (exception are if u configure BGP deterministic-med & BGP always-compare-med).
10. The three well-known mandatory paths attributes are:

ORIGIN: The ORIGIN attribute is generated by the speaker that originates the associated routing information. AS_PATH: This attribute identifies the autonomous systems through which routing information. NEXT_HOP: that defines the IP address of the router that SHOULD be used as the next hop. *Mar 7 03:32:11.715: BGP: Applying map to find origin for 200.1.4.3/32 *Mar 7 03:32:15.035: BGP: 20.2.4.7 rcv message type 4, length (excl. header) 0 *Mar 7 03:32:16.691: BGP: 20.2.4.7 send message type 4, length (incl. header) 1 9 *Mar 7 03:32:39.899: BGP: 20.2.4.1 rcv message type 4, length (excl. header) 0 *Mar 7 03:32:43.691: BGP: 20.2.4.1 send message type 4, length (incl. header) 1 9 *Mar 7 03:32:58.691: BGP: 20.2.4.2 send message type 4, length (incl. header) 1 9 *Mar 7 03:32:58.699: BGP: 20.2.4.2 rcv message type 4, length (excl. header) 0