Cisco 350-401 - Implementing Cisco Enterprise Network Core Technologies (350-401 ENCOR) v1.2

The correct answer is A.

Block HTTP traffic (TCP port 80)

Source: 10.10.10.1

Destination: any

Permit all other traffic

ip access-list extended 100

deny tcp host 10.10.10.1 any eq 80

permit ip any any

deny tcp host 10.10.10.1 any eq 80 → Blocks HTTP traffic from 10.10.10.1 to any destination

permit ip any any → Allows all other traffic

This perfectly matches the requirement.

B. ip access-list extended 10 ❌ Invalid — extended ACLs use ranges 100–199 or named ACLs, not 10

C. ip access-list extended NO_HTTP ❌ Missing permit ip any any → implicit deny all at the end blocks everything

D. deny tcp host 10.10.10.1 eq 80 any ❌ Incorrect syntax/order

eq 80 is applied to destination port, not source

This line is malformed and does not match HTTP filtering correctly

ACL evaluation rules:

Top-down processing

First match wins

Implicit deny all at the end

Correct pattern for “block one thing, allow rest”:

deny < specific traffic >

permit ip any any

Solution:

VERIFICATION: -

OR

A REST API request that lacks required authentication information is rejected by the server before the requested operation is executed. REST APIs commonly use HTTP status codes to communicate request success or failure. When authentication credentials, API tokens, session cookies, or authorization headers are missing or invalid, the server normally returns a client-error response in the 4xx range. Common examples include 401 Unauthorized, meaning authentication is required or failed, and 403 Forbidden, meaning the server understood the request but refuses access because the requester lacks permission. The server does not authenticate based only on source IP unless a separate IP-based access-control mechanism has been deliberately configured, so option A is not generally correct. The server also does not normally keep the HTTP transaction open indefinitely waiting for credentials, so option B is wrong. Option C is dangerous and wrong: APIs should not downgrade unauthenticated requests into guest execution unless an endpoint is intentionally public. In ENCOR automation, REST API security requires explicit authentication and authorization, usually over HTTPS/TLS. References/topics: ENCOR Automation, REST APIs, HTTP status codes, API authentication, tokens, Cisco Catalyst Center API behavior.

Solution:-

Copy run start

Solution:

R1

Config t

Int et0/0

Ip flow monitor Monitor-R1Flow input

Ip flow monitor Monitor-R1Flow output

Exit

Ip sla 1

Icmp-echo 10.12.1.2

Freq 300

Ip sla schedule 1 life foreve start-time now

Sw1

Config t

Monitor session 12 source vlan 12

Monitor session 12 destination interface et1/3

Solution:

R1

en

Conf t

Router ospf 10

Router-id 10.x.x.x – lo0 address

Int range lo0, e0/0-1

Ip ospf 10 area 0

Exit

wr

R2

Router ospf 10

Area 10 range 10.1.0.0 255.255.0.0

exit

wr

R3

Router ospf 10

Area 10 range 10.2.0.0 255.255.0.0

Exit

Wr

OR

Solution:

R3

Config#int et0/1

config-if#ip ospf priority 255

wr

R20

clear ip ospf process

yes

R10

int et0/0

ip ospf priority 0

wr

R2

clear ip ospf process

yes

Solution:

Sw10

config t

no int po2

int et0/0

channel-group 2 mode active

no shut

spanning-tree vlan 10a pri 0

wr

Solution:

R1

config t

flow record NetFlow-Record

match ipv4 source address

match ipv4 destination address

collect country bytes

flow exporter NetFlow-Exporter

destination 10.10.1.10

transport udp 9996

flow monitor NetFlow-Monitor

record NetFlow-Record

exporter NetFlow-Exporter

exit

int et0/0

ip flow monitor NetFlow-Monitor input

ip sla 1

http get http://10.10.1.100

frequency 600

exit

ip sla schedule 1 start-time now

wr

Sw1

config t

monitor session 2 source int e0/0

monitor session 2 source int et0/2

monitor session 2 destination interface e1/0

wr