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

Chef: A, B

SaltStack: C, D

Chef is commonly associated with Ruby-based configuration management. Chef recipes and cookbooks are written using a Ruby-based domain-specific language, and the tool describes desired infrastructure state in a declarative manner. Therefore, “declarative” and “uses Ruby” map to Chef. SaltStack is written primarily in Python and is commonly described as more procedural and execution-oriented than purely declarative tools. Salt states can define desired configuration, but Salt is also known for remote execution, event-driven automation, and procedural orchestration workflows. Therefore, “uses Python” and “procedural” map to SaltStack. In ENCOR automation, the objective is not to become a Chef or SaltStack developer, but to recognize major automation/orchestration tools and their characteristics. Cisco exams commonly compare Ansible, Puppet, Chef, and SaltStack by language, agent model, execution method, and configuration style. Chef is Ruby/cookbook/recipe oriented; SaltStack is Python/minion/remote-execution oriented. References/topics: ENCOR Automation, orchestration platforms, Chef, SaltStack, declarative versus procedural automation, Ruby, Python.

The correct answer is A. json_final = json.loads(json_data).

When using Python on Cisco devices:

The cli() function returns output as a string

To work with structured data, the string must be converted into a JSON object (Python dictionary)

The exhibit shows:

json_data = cli(cmd)

json_final = json.import(json_data)

This is incorrect because:

json.import() is not a valid Python function

The script fails to convert the JSON string into a Python object

json_final = json.loads(json_data)

json.loads() parses a JSON-formatted string

Converts it into a Python dictionary

Enables access using keys like:

json_final[ " TABLE_intf " ][ " ROW_intf " ][0] [ " prefix " ]

B. This line assumes the JSON is already converted into an object. It does not fix the conversion issue.

C. Incorrect syntax and unnecessary; json is already imported properly.

D. Just defines a command string; does not address JSON conversion.

Always remember the difference:

json.loads() → String → Python object

json.dumps() → Python object → String

Correct Automation Workflow:

Run CLI command

Capture output (string)

Convert using json.loads()

Parse using dictionary keys

This is a core concept for Cisco automation questions in the ENCOR exam.

The correct answer is D. print(json_object[ " TABLE_intf " ][ " ROW_intf " ][0] [ " prefix " ]).

Parsing JSON output from Cisco devices

Using Python to extract structured data

Understanding how CLI output is converted into JSON format

The command used:

show ip int brief | json

returns structured JSON data.

The JSON hierarchy shown in the exhibit:

{

" TABLE_intf " : {

" ROW_intf " : [

{ " intf-name " : " Vlan100 " , " prefix " : " 192.168.10.1 " , ... },

{ " intf-name " : " Vlan200 " , " prefix " : " 192.168.20.1 " , ... },

...

]

}

}

Important Observations:

ROW_intf is a list (array) of interface objects.

Each object contains fields like " prefix " (IP address).

VLAN 100 is used for management and appears first in the list.

Python Code Analysis:

json.loads() converts JSON string into a Python dictionary → json_object

To access VLAN100 IP:

json_object[ " TABLE_intf " ][ " ROW_intf " ][0] [ " prefix " ]

Why Option D is Correct:

Uses the correct variable ( json_object )

Correctly navigates dictionary → list → element → key

Index [0] corresponds to Vlan100 (management VLAN)

A & B: Use json.dumps incorrectly (this function converts Python → JSON, not for accessing data)

C: Uses index [1] , which refers to Vlan200, not VLAN100

When working with Cisco JSON output:

Identify list vs dictionary

Use indexing for lists ( [0] )

Use keys for dictionaries ( [ " key " ] )

Correct Pattern:

json_object[ " parent " ][ " child " ][index] [ " field " ]

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:

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:

R2

config t

username NetworkAdmin privilege 15 password CiscoENCOR

line vty 0 4

login local

transport input telnet rlogin

exec-timepit 20

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:

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

Verification:

OR

Solution:

R2

R3

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:

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:

R10

Copy run start

R20

Copy run start

Verification:

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:

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

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:

VERIFICATION: -

OR

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:

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:

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

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:

Copy run start

Verification:

OR

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:

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

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:-

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:

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:-

Copy run start

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