JN0-649 Enterprise Routing and Switching Professional (JNCIP-ENT) Questions and Answers

Level 1/2 routers automatically inject a default route to the nearest Level 1 router. It's the other way around

https://www.juniper.net/documentation/us/en/software/junos/stp-l2/topics/topic-map/spanning-tree-configuring-mstp.html

BUM Traffic Forwarding

Junos devices that use MPLS encapsulation for EVPNs can only use ingress replication at this time.

Ingress replication means, to flood traffic to remote PE routers, the traffic has to be replicated, once for each remote PE router.

The EVPN label for this BUM traffic is learned per PE router from the route type 3, inclusive multicast Ethernet tag route.

This table shows the format of the inclusive multicast Ethernet tag route.

All-Active Redundancy (4)

This diagram shows the format of the type 1 route, A-D route per ES. The split horizon label is advertised as part of an extended community attached to the type 1 route. The split horizon label is also called the ESI label. The extended community also indicates what type of redundancy mode is used for this given ESI: single-active represented by binary 1 or active-active represented by binary 0.

For specifying the BGP community attribute only, you also can specify community-ids as one of the following well-known community names defined in RFC 1997:

no-advertise—Routes containing this community name are not advertised to other BGP peers.

no-export—Routes containing this community name are not advertised outside a BGP confederation boundary.

no-export-subconfed—Routes containing this community are advertised to IBGP peers with the same AS number, but not to members of other confederations.

llgr-stale—Adds a community to a long-lived stale route when it is readvertised.

no-llgr—Marks routes which a BGP speaker does not want to be retained by LLGR. The Notification message feature does not have any associated configuration parameters.

https://www.juniper.net/documentation/us/en/software/junos/bgp/topics/ref/statement/community-edit-routing-options.html

For a device configured for 802.1X authentication, specify that when the device receives an Extensible Authentication Protocol Over LAN (EAPoL) Access-Reject message during the authentication process between the device and the RADIUS authentication server, supplicants attempting to access the LAN are granted access and moved to a specific bridge domain or VLAN. Any bridge domain, VLAN name or VLAN ID sent by a RADIUS server as part of the EAPoL Access-Reject message is ignored.