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.

A is correct because you need to configure BGP multihop to enable redundancy for the EBGP peering

between the two routers. BGP multihop is a feature that allows BGP peers to establish a session over

multiple hops, instead of requiring them to be directly connected1. By default, EBGP peers use a

time-to-live (TTL) value of 1 for their packets, which means that they can only reach adjacent

neighbors1. However, if you configure BGP multihop with a higher TTL value, you can allow EBGP

peers to communicate over multiple routers in between1. This can provide redundancy in case of a

link failure or a router failure between the EBGP peers.

B is correct because you need to configure loopback interface peering to enable redundancy for the

EBGP peering between the two routers. Loopback interface peering is a technique that uses

loopback interfaces as the source and destination addresses for BGP sessions, instead of physical

interfaces2. Loopback interfaces are virtual interfaces that are always up and reachable as long as the

router is operational2. By using loopback interface peering, you can avoid the dependency on a

single physical interface or link for the BGP session, and use multiple paths to reach the loopback

address of the peer2. This can provide redundancy and load balancing for the EBGP peering.

C is correct because you need to configure routes for the peer loopback interface IP addresses to

enable redundancy for the EBGP peering between the two routers. Routes for the peer loopback

interface IP addresses are necessary to ensure that the routers can reach each other’s loopback

addresses over multiple hops2. You can use static routes or dynamic routing protocols to advertise

and learn the routes for the peer loopback interface IP addresses2. Without these routes, the routers

will not be able to establish or maintain the BGP session using their loopback interfaces.

The maximum allowable MTU size for a default GRE tunnel without IPv4 traffic fragmentation is 1476

bytes1. This is because GRE packets are formed by the addition of the original packets and the

required GRE headers1. These headers are 24-bytes in length and since these headers are added to

the original frame, depending on the original size of the packet we may run into IP MTU

problems1. The most common IP MTU is 1500-bytes in length (Ethernet)1. When the tunnel is

created, it deducts the 24-bytes it needs to encapsulate the passenger protocols and that is the IP

MTU it will use1. For example, if we are forming a tunnel over FastEthernet (IP MTU 1500) the IOS

calculates the IP MTU on the tunnel as: 1500-bytes from Ethernet - 24-bytes for the GRE

encapsulation = 1476-Bytes1.

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.

Option A is correct. Creating multiple areas in OSPF can help to reduce the convergence time . This is

because changes in one area do not affect other areas, so fewer routers need to run the SPF

algorithm in response to a change.

Option D is correct. Creating multiple areas in OSPF can help to reduce Link State Advertisement

(LSA) flooding across the network. This is because LSAs are not flooded out of their area of origin.