Exam 350-401 topic 1 question 425 discussion

The answer is wrong. "running": null Name:100 Permit Match

I would put the following: 1. “running”: null <<<<target running config 2. “name”:”100″, <<<<< prefix list name "100" 3. “seq_no”: <<<<<<< there is no permit command within a route map. this is the only logical selection here. 4. “match”: again within a route map we can either set, or match.

"running": null Name:100 Permit Match This is a very tricky question. For any production route-map I have ever created and as per Cisco's documentation, you of course can and do specify a permit | deny, without this all traffic that is matched is implicitly denied in the route-map and where it is applied, why some people are stating permit | deny is not used in a route-map is very strange misinformation, it is a key component in the traffic engineering process. However in rare cases you can create a route-map without a permit or deny statement, specifying a sequence number only which is used to update an existing route-map entry. It seems too odd that Cisco would ask you to update an existing route-map when no other question I've come across asks for even basic route-map configuration. Surely we create the entry using a standard 'permit' here. https://www.cisco.com/c/en/us/td/docs/security/asa/asa84/configuration/guide/asa_84_cli_config/route_maps.pdf

checked with real RPC model: the correct order : running name seq_no match

given answer is incorrect "running": null "name":"100", "permit": "match": https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-KB/16-02/5200-1671_K_MRG/content/ch11s06.html#:~:text=If%20the%20route%2Dmap%20has%20more%20than%20one%20sequence%2C%20the%20sequence%20number%20is%20required%3A%20route%2Dmap%20name%20permit%20%7C%20deny%20seq%20seq%2Dnum%20. ...........

i think it's like this running name Seq match

"running": null Name:100 Permit Match NETCONF <edit-config> Request: CLI Format <?xml version="1.0" encoding="UTF-8"?> <rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <edit-config> <target> <running/> </target> <config>

Is it a Resconf sample?

- "running": null - "name":"100" - "permit" - "match" TIP: runapem

1 - running 2 - name 3 - seq (this is a route-map) 4 - match the acl/prefix for the route-map.

Answer: 1. “running”: null 2. “name”:”100″, 3. “seq_no”: 4. “match”:

Suggested answer is wrong. If I understand correctly, correct should be: * "running": null * "name":"100" * "permit" * "match" The order in the route-map is a bit odd, the "match" part comes first and after that comes the "set" part... But, in the running-config (that is the target) in IOS this would be: * ip prefix-list 100 seq 10 permit 0.0.0.0/0 <- name of prefix-list is "100" * route-map Routes permit 10 <- "permit" 10 * match ip address prefix-list 100 <- "match" the prefix-list "100" * set local-preference 200