Cisco CCIE Service Provider Written

ISIS updates exchange between trigger router and black hole router ✘ EBGP updates exchange between trigger router and black hole router ✘ None of above ✘ OSPF updates exchange between trigger router and black hole router ✔ IBGP updates exchange between trigger router and black hole router ✔

Route tagging is one of the techniques used by RTBH ✘ It is used for BGP authentication ✘ It cannot work with static routes ✘ It uses extended ACLs for blocking attacks by creating a black hole ✔ Before configuring RTBH. LDP must be enabled on the interface ✔

Subsequent Address Family identifier (SAFI) provides additional information about the type of the NetworkLayer ports carried in the BGP update Address Family identifier (AFI) field carries the identity of the Network Layer ports for which the BGP speaker intends to advertise multiple paths Subsequent Address Family identifier (SAFI) provides additional information about the type of the Network Layer Reachability Information carried in the attribute Address Family identifier (AFI) carries the identity of the Network Layer protocol for which the BGP speaker intends to advertise multiple paths

AFI is 2, SAFI is 96 ✘ AFI is 2, SAFI is 64 ✘ AFI is 1, SAFI is 64 ✘ AFI is 1, SAFI is 128 ✔ AFI is 2, SAFI is 128 ✔

cluster ID ✘ Weight ✘ MED ✘ local preference ✔ aggregate ✔

MD5 has been used by BGP to encrypt BGP update packets. ✘ BGP uses a message-digest algorithm to authenticate BGP peers ✘ A plain-text password authentication is an option of BGP authentication ✘ EBGP peers authentication is faster than IBGP peers authentication ✔ BGP uses public key and private key to authenticate BGP peers. ✔

TCP ✘ UDP ✘ HTTP ✘ Multicast ✔

immediately after receiving the first packet on the shared tree for a given (S, G) ✘ after receiving over 1 kb/s traffic on the shared tree for a given (S, G) ✘ 10 seconds after receiving the first packet on the shared tree for a given (S, G) ✘ 30 seconds after receiving the first packet on the shared tree for a given (S, G) ✔ after receiving over 10 kb/s traffic on the shared tree for a given (S, G) ✔

Receivers are "registered" with RP by their first-hop router ✘ It supports shared trees only assuming all hosts want the multicast traffic ✘ From the RP, traffic flows down a Source Tree to each receiver ✘ It does not support all underlying unicast routing protocols like BGP ✔ Receivers are "joined" to the Shared Tree (rooted the rp) by their local Designated Router (DR) ✔

multicast temporary node local ✘ multicast temporary site local ✘ unicast permanent link local ✘ multicast permanent node link local ✔ multicast permanent site local ✔