Exhibit shows that the acl is applied to the interface

Inbound access list ENARSI-ACL

Not sure what the correct answer is but applying the acl to the interface is wrong

Diagram is misleading , the two circles suggest eBGP but path in neighbor table suggests iBGP.

RB is clearly in AS65101

the two circles and the answer choices suggest RD, RE, and RF are in AS65201.

i think there is an issue with the "correct" answer.

It should be:

"no sequence 30" and then put this entry as sequence 5. 
Otherwise you put the same entry as sequence 5 as already set in sequence 30

How do you configure a different interface to send netflow records?  

The destination is on the same subnet as the mgmt interface (gig 0).

Gig 0 is isolated from other vrf's it is unlikely that other interfaces will be able to send traffic to 192.168.100.17.  This is a private ip address on the Mgmt-intf vrf.  

The more likely solution is to fix a connectivity problem between two devices on the same vrf and network segment.

IP addressing problem in diagram. Are both devices directly connected but in different subnets?


It is not the filename.
Switch is a tftp client, no need to configure it for server function.


Not sure about the other two.  
Adding a route in the switch won't help if there is no router.  I suppose you could specify an exit interface of e0/1 but then you would have to do the same in the server.

Using TFTP Server IP address 10.0.0.0.1?  THats the switch address but who knows the ip addressing in the exhibit seems wrong.

IF this is how the question is intended than an better explanation is warranted.

SNMPv3 is the only version that supports authentication.


ACL related problems would deny traffic.  You would not see an AUTHFAIL if the ACL was a problem.

the community strings are valid.

You cannot configure SNMP authentication on SNMPv2 and below

Only option to support authentication failures is to update to SNMP v3

same question and answers

Diagram has router a twice, no router b.

R3 show that gig 0/1 172.16.250.2 is up up. This is the interface to R2 gig 0/0
R3 shows 172.16.250.14 is connected to gig 0/2.  This address doen't exist on exhibit diagram.


Answer is correct.  question is misleading because configs are nor correct.

Routing table of R4 shows that R4 does not know about 192.168.1.0/30 or 192.168.2.0/24.

Traceroute shows that there is a routing problem between R1 and R2.
R1 knows how to get to R2. This is evident in R3's routing table which shows 172.16.0.0/16 via R1. This also proves that R1 and R2 are eigrp neighbors.

putting a static route on R4 wont fix the problem between R1 and R2.

Redistributing routes into EIGRP does not work without assigning a metric. The option to use a route map to set a metric does not work.  No where is the route map tied to eigrp.