Free and Premium Cisco 350-401 Dumps Questions Answers

Solution:

R30

Config t

router ospf 100

router-id 10.0.1.30

int ran lo0 , e0/0-1

ip ospf 100 a 0

exit

int et0/2

ip ospf 100 a 50

exit

router ospf 30

area 50 range 10.10.0.0 255.255.192.0

area 50 range 10.50.0.0 255.255.192.0

end

wr

Solution: -

Solution:

Solution on R1:

R1# copy run start

Verification:

OR

Solution:

R30

Config t

router ospf 100

router-id 10.0.1.30

int ran lo0 , e0/0-1

ip ospf 100 a 0

exit

int et0/2

ip ospf 100 a 50

exit

router ospf 30

area 50 range 10.10.0.0 255.255.192.0

area 50 range 10.50.0.0 255.255.192.0

end

wr

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:

R2

R3

Solution:

R1

config

flow exporter Export-NetFlowENCOR

transport udp 2055

ip sla schedule 100 life forever start-time now

wr

Sw1

monitor session 11 source interface e0/2

monitor session 11 destination interface et1/1

wr

OR

Solution:

R1

Config t

Flow exporter Export-NetFlowENCOR

destination 10.10.1.110

transport udp 2055

exit

flow moni Monitor-NetFlowENCOR

exit

ip sla 1

http

frequ 300

exit

ip sla schedule 1 life forever start-time now

wr

SW1

Config t

Monitor session 7 source interface e0/0

Monitor session 7 destination interface e1/1

End

Wr

Solution:

R2

show ip access-list

config t

ip access-list extended 151

5 permit eigrp any any

wr

R3

config t

ip access-list extended 100

permit tcp 192.168.211.0 0.0.0.255 any eq 22

class-map match-any SSH

match access-group 100

policy-map CoPP

class SSH

police 8000 conform-action transmit exceed-action drop

control-plane

service-policy input CoPP

Solution:

VERIFICATION: -

OR

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

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

Solution:

Sw10

config t

no int po20

int et0/0

channel-group 20 mode active

no shut

spanning-tree vlan 20 pri 0

wr

Verification:-

Solution:

Copy run start

Copy run start

Copy run start

Verification:-

OR

Solution:

R22

int tun0

vrf forwarding FINANCE

ip add 10.10.10.2 255.255.255.0

tunn source e0/0

tunnel dest 209.165.200.230

no shut

ip route vrf FINANCE 10.10.111.0 255.255.255.0 tunn0

int et0/1

vrf forwarding FINANCE

ip address 10.22.22.1 255.255.255.252

wr

Verification:-

Solution:-

Copy run start

Solution:

router bgp 10

bgp router-id 10.1.1.111

no bgp defa ipv4-unicast

nei 209.165.200.226 remote-as 20

nei 209.165.202.130 remote-as 30

address-family ipv4

neigh 209.165.200.226 activate

neigh 209.165.202.130 activate

network 10.1.1.10 mask 255.255.255.255

network 209.165.201.10 mask 255.255.255.255

network 209.165.201.20 mask 255.255.255.255

wr

Sw10

Config t

no int po1

default int ran et0/0-2

int ran e0/0-2

switchport trunk encap dot1q

switchport mode trunk

channel-group 1 mode active

no shut

wr

Solution:

R2

config t

username NetworkAdmin privilege 15 password CiscoENCOR

line vty 0 4

login local

transport input telnet rlogin

exec-timepit 20

Solution:-

Default int range et0/0-1

Int range e0/0 – 1

Sw trunk encap dot1

Switch mode trunk

Channel-group 2 mode passive

No shut

Spanning-tree vlan 10 priority 0

Spanning-tree vlan 30 priority 0

Solution:

R30

Config t

router ospf 10

router-id 10.0.1.30

int ran lo0 , e0/0-1

ip ospf 10 a 0

exit

int et0/2

ip ospf 10 a 50

exit

router ospf 10

area 50 range 10.10.0.0 255.255.128.0

area 50 range 10.50.0.0 255.255.128.0

end

Solution:

R10

Copy run start

R20

Copy run start

Verification:

Solution:

Copy run start

Verification:

OR

Solution:

Copy run start

Verification:

OR

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:

R30

show ip access-list

config t

ip access-list extended 120

5 permit eigrp any any

wr

R20

config t

ip access-list extended 100

permit tcp 192.168.25.0 0.0.0.255 any eq 23

class-map match-any TELNET

match access-group 100

policy-map CoPP

class TELNET

police 10000 conform-action transmit exceed-action drop

control-plane

service-policy input CoPP

wr

Solution:

R22

config t

int tunn0

vrf forwarding FINANCE

ip add 10.11.22.2 255.255.255.0

tunn so e0/0

tunn dest 209.165.200.230

no shut

int et0/1

vrf forward FINANCE

ip add 10.22.22.1 255.255.255.252

no shut

ip route vrf FINANCE 10.10.111.0 255.255.255.0 tunn0

wr

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:

R3

Int e0/1

Ip ospf priority 255

End

Copy run start

R2

Int e0/1

Ip ospf network point-to-point

End

Copy run start

R10

Int e0/0

Ip ospf network point-to-point

End

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

In Locator/ID Separation Protocol, the ingress tunnel router is responsible for encapsulating traffic from an endpoint identifier toward the correct routing locator. When the ITR does not already have an EID-to-RLOC mapping in its local map cache, it must request that mapping through the LISP control plane. The component that receives map requests from ITRs is the Map Resolver. Therefore, option A is correct. A routing locator is not a query target; it is the routable address representing the location of an EID in the underlay or routing infrastructure. A proxy ingress tunnel router is used to connect non-LISP sites toward LISP sites by acting on behalf of non-LISP sources. A proxy egress tunnel router provides reachability in the reverse direction, helping LISP sites communicate with non-LISP destinations. Neither PITR nor PETR is the normal answer to an ITR mapping-resolution request. The core ENCOR point is the separation between endpoint identity and routing location, with map resolution handled by the LISP control plane. References/topics: ENCOR Architecture, LISP, ITR, Map Resolver, EID-to-RLOC mapping, SD-Access control plane concepts.

The correct answer is A. Interface FastEthernet0/0 is configured in VRF CUST-A, so the ARP entry is also in that VRF.

In Cisco VRF implementations, ARP entries are maintained separately per VRF, not in the global routing table. Cisco documentation states that with Multi-VRF CE, ARP entries are learned in separate VRFs, and the user can display them for a specific VRF. Cisco also documents the command show ip arp vrf < vrf-name > to display the ARP table for a specified VRF.

That means if the interface belongs to VRF CUST-A, a normal global show ip arp 192.168.12.2 may not display the entry, even though ping vrf CUST-A 192.168.12.2 succeeds. The ARP entry exists, but it is stored under the CUST-A VRF ARP table, not the global ARP table.

B. When VRFs are used, ARP protocol is disabled in the global routing table. This is incorrect. ARP is not disabled; it is simply VRF-aware and tracked separately per VRF.

C. When VRFs are used, ARP protocol must be enabled in each VRF. This is incorrect. There is no separate requirement to manually enable ARP in each VRF for normal operation in this context.

D. The ping command must be executed in the global routing table. This is incorrect because Cisco supports pinging within a specific VRF, and the exhibit already shows the use of ping vrf CUST-A .

ENCOR exam point:

With VRF-aware services, always remember:

Routing table = per VRF

ARP table = per VRF

Verification commands often require the VRF keyword

A traditional WAN does not rely on the same overlay, controller-based policy distribution, tunnel encapsulation, or centralized abstraction model used by SD-WAN. Because of that, one valid benefit is lower data plane overhead. SD-WAN commonly adds encapsulation, encryption, tunnel metadata, and policy-based forwarding logic across WAN edge devices, which creates additional processing and packet overhead compared with a more direct traditional WAN path. The second benefit is lower control plane abstraction. Traditional WAN routing is usually built directly with protocols such as OSPF, EIGRP, BGP, static routing, MPLS VPN routing, or other conventional mechanisms. That makes the control-plane operation less abstracted than SD-WAN, where controllers calculate, distribute, and enforce policies across WAN edges. Options A, C, and E are stronger SD-WAN benefits. SD-WAN is designed to standardize policy, simplify operational management through centralized control, and improve application-aware path selection or failover. Traditional WAN can be simpler in small environments, but it does not inherently provide comprehensive standardization or faster fault detection. References/topics: ENCOR Architecture, WAN design, SD-WAN overlay, control plane abstraction, data plane encapsulation overhead.

The ntp broadcast command under an interface configures the router to send NTP broadcast packets out that interface. In this exhibit, the command is applied under GigabitEthernet0/1, so R1 will broadcast NTP updates onto that connected segment. Option C is therefore correct. Option A would require the device to be configured as an NTP broadcast client, commonly with ntp broadcast client, so merely configuring ntp broadcast does not make the interface receive broadcast time updates. Option B is incomplete because the ntp server commands configure R1 to use specified unicast NTP servers as time sources, but the interface-level question is specifically about the effect of ntp broadcast. Option D is wrong because a single ntp broadcast command does not configure both send and receive behavior. The ENCOR point is that NTP can operate in different modes: unicast client/server, broadcast server, and broadcast client. The command location matters: global ntp server points to time sources, while interface ntp broadcast advertises time to a segment. References/topics: ENCOR Infrastructure Services, NTP, time synchronization, interface-level NTP broadcast behavior.