Pass the Cisco CCNP Enterprise 350-401 Questions and answers with CertsForce

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

1 and 3 – Configuration

4 and 5 – Orchestration

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 gethttp://10.10.1.100

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:

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:

R2

R3

The Cisco Catalyst Center Intent API is a northbound API that allows external systems, applications, and automation workflows to interact with Catalyst Center at an abstracted intent level. It is not primarily a device-by-device command interface. The purpose of an intent-based platform is to let administrators or applications express the desired business or network outcome, while the controller translates that intent into the required operational changes, workflows, and device-level configurations. That makes “northbound API” and “business outcome oriented” the correct selections. “Procedural” is incorrect because procedural automation describes step-by-step instructions, while an intent API focuses on the desired result. “Device-oriented” is also wrong because device-level control is normally handled through southbound mechanisms or lower-level APIs and protocols. “Southbound API” is incorrect because southbound communication is controller-to-device communication, while the Intent API is used above the controller by applications and integrations. The ENCOR automation concept is that Catalyst Center exposes intent-based RESTful northbound APIs for network discovery, assurance, provisioning, and policy workflows. References/topics: ENCOR Automation, Cisco Catalyst Center, Intent API, northbound APIs, intent-based networking, controller abstraction.