is 172.16.1.3 an FTP server?  Or is it supposed to be the TACACS Server?

It appears the exhibit forgot to name the route-maps.

the route-map is named 'deny'  

the second route-map is named 'permit'

neither route-map contains a permit or deny clause.  GNS3 shows that Route-maps can be configured without a permit or deny clause.  Configuring a route-map this way results in an implicit permit.

The exhibit is either wrong, or the answers are wrong.

If we assume the route-maps are intended to be named 'deny' and 'permit' we do not know which route map is applied.




!!! Route-map named 'deny' with no permit/deny clause defaults to permit
R4(config)#route-map ?
  WORD  Route map tag

R4(config)#route-map deny ?
  <0-65535>  Sequence to insert to/delete from existing route-map entry
  deny      Route map denies set operations
  permit    Route map permits set operations
  <cr>

R4(config)#route-map deny 10
R4(config-route-map)#match address 10
R4(config-route-map)#do sh route-map
route-map deny, permit, sequence 10
  Match clauses:
    ip address (access-lists): 10
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes

!!! route-map named 'deny' with a deny clause denies any match.

R5(config)#route-map deny deny 10
R5(config-route-map)#match address 10
R5(config-route-map)#do sh route-map
route-map deny, deny, sequence 10
  Match clauses:
    ip address (access-lists): 10
  Set clauses:
  Policy routing matches: 0 packets, 0 bytes

Line 30 of ACL is wrong.  Should be host 2001:abc:20:2:2::2
or the answer is to remove line 70 from the acl

Default-information originate can only be configured under ospfv3 ipv6 address-gamily instance.

R1(config)#ipv6 unicast-routing
R1(config)#router ospfv3 1

R1(config-router)#default?
default

R1(config-router)#address-family ipv6 unicast
R1(config-router-af)#default?
default  default-information  default-metric

R1(config-router-af)#default-information ?
  originate  Distribute default route

There is no need for a flow exporter on R1.  The problem is that the netflow collector cannot receive flows from R1.

only making changes to R3, the secondary link is not the correct choice.

R1 Flow exporter shows the traffic destined to 10.60.66.66 port 1090, the actual IP address of the collector is 10.66.66.66.  This needs to be corrected.

The other problem is that R4 is the primary link and has an ACL blocking udp 1090.

there is a debug log shown in the exhibit not an syslog.

It would make more sense, to configure "service timestamps debug datetime localtime msec"

None of the answers are correct.

le is not the same as lower than

le 23 is not the same as lower than 23

The clue to the answer is provided by the question. "Not all guests"

Allow 10.66.46.0/23 should be the correct answer in my opinion. The interface itself is also in the /23 subnet, so the entire range should also be taken into account in the ACL.

Hello,

Do you know if “Tab” and/ or “?” are working on the ENARSI-Exam?

Thanks in advance

There is no reason to believe a local user account has been created on R2.

there is no password command in global config.  there is enable password and password under line config.  Still no reference to a local user account on the device.

All configs lead toward a telnet session using the password under the vty lines with enable secret to enter privileged mode.

login local will not work without a user account on the device.

vty has 3 options
no login <-- gives access without authentication
login <-- uses vty password for authentication
login local <-- prompts for a username and password

the only way to get connection refused is by

line vty 0 4
trans in none

or

line vty 0 4
no exec