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

exhibit show that R1 is attempting to connect to 10.221.10.10 and reveals a connect error

fixing the diagram will show that a static route out e 0/1 will fix the problem

R1 has two interfaces labeled E0/0

an ospf stub area only prevents external routes.  Type-3 (summary LSAs) are permitted in an ospf stub area.

you need the command 'area 1 stub no-summary'

Tough question.

A permit any statement is modifying the acl, which is prohibited.

a continue statement on the route map does nothing


A permit 20 is route-map syntax (20 permit would be for an ACL).  Adding a route-map entry to permit anything not matched by route-map entry 10  is the correct option.

Keywords here are 'only ever uses the MPLS B Network'. Any option that sets a preferences is invalid.

Modifying the weight, local preference or AS Path prepending allows traffic to go through MPLS A during an outage.

AS Path filtering is the only option.  It allows connectivity to Branch A, but would prevent Branch b from learning routes from MPLS A.

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