The exhibit shows the output of the command show vlans brief, which displays brief information

about VLANs and their associated interfaces1.

The output has four columns: Routing instance, VLAN name, Interfaces, and Tagging.

The * symbol indicates that the interface is active, meaning that it is up and forwarding traffic1. This

can be verified by the command show interfaces terse, which displays the status of the interfaces2.

The output shown in the exhibit is the result of the command “show ip bgp neighbor 10.36.1.4

received-routes”, which displays all received routes (both accepted and rejected) from the specified

neighbor.

Option A is correct, because the routes displayed have traversed one or more autonomous systems.

This can be seen from the AS_PATH attribute, which shows the sequence of AS numbers that the

route has passed through. For example, the route 10.0.0.0/8 has an AS_PATH of 65001 65002, which

means that it has traversed AS 65001 and AS 65002 before reaching the local router.

Option B is correct, because the output shows routes that were received prior to the application of

any BGP import policies. This can be seen from the fact that some routes have a status code of “r”,

which means that they are rejected by an import policy. The “received-routes” keyword shows the

routes coming from a given neighbor before the inbound policy has been applied. To see the routes

after the inbound policy has been applied, the “routes” keyword should be used instead.

Option C is incorrect, because the output does not show routes that are active and rejected by an

import policy. The status code of “r” means that the route is rejected by an import policy, but it does

not mean that it is active. The status code of “>” means that the route is active and selected as the

best path. None of the routes in the output have both “>” and “r” status codes.

Option D is incorrect, because the routes displayed are not being learned from an IBGP peer. An IBGP

peer is a BGP neighbor that belongs to the same AS as the local router. The output shows that the

neighbor 10.36.1.4 has a remote AS of 65001, which is different from the local AS of 65002.

Therefore, the neighbor is an EBGP peer, not an IBGP peer.

A) On R1, enable Level 1 on the ge-0/0/1 interface. In IS-IS, both levels (Level 1 and Level 2) are

enabled by default when you enable IS-IS on an interface1. Level 1 systems route within an area2. If

the destination is outside an area, Level 1 systems route toward a Level 2 system2. Therefore,

enabling Level 1 on the ge-0/0/1 interface on R1 would allow packets to reach from R1 to R3.

D) On R3 enable Level 1 on the ge-0/0/4 interface Similarly, enabling Level 1 on the ge-0/0/4

interface on R3 would allow packets to reach from R1 to R3.

These explanations are based on the IS-IS configuration documents and learning resources available

at Juniper Networks1 and Cisco34.

IS-IS (Intermediate System to Intermediate System) is a routing protocol that is designed to move

information efficiently within a computer network12. It supports multiple protocol topologies,

including IPv4, IPv6, and multicast12. Therefore, options C, E, and D are correct.

Option B is correct. Filter-based forwarding (FBF), also known as Policy Based Routing (PBR), uses the

forwarding routing instance type12.

Option C is correct. Routing Information Base (RIB) groups are used to copy routes from one routing

table to another34. In the context of FBF, RIB groups can be used to copy routes from the inet.0

routing table34.

Option A is incorrect. FBF does not use the no-forwarding routing instance type15.

Option D is incorrect. RIB groups are not used to hide routes in the inet.0 routing table34. They are

used to share or copy routes between different routing tables34.