300-410 ENARSI: Implementing Cisco Enterprise Advanced Routing and ServicesDemo

By Cisco · Question Mode

QuestionQ386

Layer 3 Technologies

An engineer configures PBR on R5 and needs to create a policy that matches traffic destined for 10.10.10.0/24 and forwards it to 10.1.1.1. This traffic must also have IP precedence set to 5. All remaining traffic must be forwarded to 10.1.1.2 and have IP precedence set to 0. Which configuration satisfies these requirements?

  • A access-list 100 permit ip any 10.10.10.0 0.0.0.255route-map CCNP permit 10match ip address 100set ip next-hop 10.1.1.1set ip precedence 5!route-map CCNP permit 20set ip next-hop 10.1.1.2set ip precedence 0
  • B access-list 100 permit ip any 10.10.10.0 0.0.0.255route-map CCNP permit 10match ip address 100set ip next-hop 10.1.1.1set ip precedence 0!route-map CCNP permit 20set ip next-hop 10.1.1.2set ip precedence 5!route-map CCNP permit 30
  • C access-list 1 permit 10.10.10.0 0.0.0.255route-map CCNP permit 10match ip address 1set ip next-hop 10.1.1.1set ip precedence 5!route-map CCNP permit 20set ip next-hop 10.1.1.2set ip precedence 0
  • D access-list 1 permit 10.10.10.0 0.0.0.255access-list 2 permit anyroute-map CCNP permit 10match ip address 1set ip next-hop 10.1.1.1set ip precedence 5!route-map CCNP permit 20match ip address 2set ip next-hop 10.1.1.2set ip precedence 0!route-map CCNP permit 30
Explanation

An extended ACL can match any source with destination 10.10.10.0/24. A matching route-map sequence applies its set ip next-hop 10.1.1.1 and set ip precedence 5 actions. A later permit sequence with no match clause matches all remaining packets, setting their next hop to 10.1.1.2 and their IP precedence to 0. Cisco IOS PBR uses standard ACLs for source-address match criteria, while extended ACLs can match source and destination addresses.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!