300-410 Policy-Based Routing (PBR) • Complete Question Bank
Complete 300-410 Policy-Based Routing (PBR) question bank — all 0 questions with answers and detailed explanations.
A network engineer runs the following command on Router R1:
R1# show route-map
route-map PBR-ROUTE, permit, sequence 10 Match clauses:
ip address (access-lists): ACL-PBR
Set clauses:
ip next-hop 192.168.1.2
Policy routing matches: 0 packets, 0 bytes
route-map PBR-ROUTE, permit, sequence 20 Match clauses: Set clauses:
ip next-hop 192.168.2.2
Policy routing matches: 0 packets, 0 bytes
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-ROUTE
Based on this output, what is the most likely problem?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/1 PBR-MAP
R1# show route-map PBR-MAP
route-map PBR-MAP, permit, sequence 10 Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop verify-availability 10.1.1.2 10 track 1
Policy routing matches: 150 packets, 12000 bytes
R1# show track 1 Track 1 IP SLA 1 reachability
Reachability is Down 1 change, last change 00:05:20 Latest operation return code: timeout
Tracked by:
ROUTE-MAP 0
Based on this output, what is the most likely outcome?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-TEST
R1# show route-map PBR-TEST
route-map PBR-TEST, permit, sequence 10 Match clauses:
ip address (access-lists): 110
Set clauses:
ip next-hop 192.168.100.1
Policy routing matches: 0 packets, 0 bytes
R1# show access-lists 110
Extended IP access list 110
10 permit tcp 10.0.0.0 0.255.255.255 any eq 80
20 permit tcp 10.0.0.0 0.255.255.255 any eq 443
R1# show ip route 192.168.100.1Routing entry for 192.168.100.1/32 Known via "ospf 1", distance 110, metric 20 Last update from 10.1.1.2 on GigabitEthernet0/1
Based on this output, what is the most likely reason for zero policy routing matches?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-QOS
R1# show route-map PBR-QOS
route-map PBR-QOS, permit, sequence 10 Match clauses:
ip address (access-lists): 120
Set clauses:
ip next-hop 10.0.0.2
Policy routing matches: 500 packets, 45000 bytes
R1# show access-lists 120
Extended IP access list 120
10 permit ip 192.168.1.0 0.0.0.255 any R1# debug ip policy
Policy routing debugging is on
*Mar 1 00:05:23.123: IP: s=192.168.1.100 (GigabitEthernet0/0), d=8.8.8.8, len 100, policy match *Mar 1 00:05:23.123: IP: s=192.168.1.100 (GigabitEthernet0/0), d=8.8.8.8, len 100, policy rejected
Based on this output, what is the most likely problem?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-VOICE
R1# show route-map PBR-VOICE
route-map PBR-VOICE, permit, sequence 10 Match clauses:
ip address (access-lists): 130
Set clauses:
ip next-hop 192.168.10.1
Policy routing matches: 0 packets, 0 bytes
R1# show access-lists 130
Extended IP access list 130
10 permit udp any any range 16384 32767 R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up Internet address is 10.1.1.1/24
R1# show ip route 192.168.10.1
% Network not in routing table
Based on this output, what is the most likely problem?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-MULTI
R1# show route-map PBR-MULTI
route-map PBR-MULTI, permit, sequence 10 Match clauses:
ip address (access-lists): 140
Set clauses:
ip next-hop 10.0.0.2 10.0.0.3
Policy routing matches: 200 packets, 18000 bytes
R1# show ip route 10.0.0.2
Routing entry for 10.0.0.2/32 Known via "eigrp 1", distance 90, metric 28160 Last update from 192.168.1.2 on GigabitEthernet0/1
R1# show ip route 10.0.0.3
% Network not in routing table
Based on this output, what is the most likely behavior for packets matching ACL 140?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-DEFAULT
R1# show route-map PBR-DEFAULT
route-map PBR-DEFAULT, permit, sequence 10 Match clauses:
ip address (access-lists): 150
Set clauses:
ip next-hop 10.0.0.2
Policy routing matches: 0 packets, 0 bytes
route-map PBR-DEFAULT, deny, sequence 20 Match clauses: Set clauses: Policy routing matches: 0 packets, 0 bytes
R1# show access-lists 150
Extended IP access list 150
10 permit ip 192.168.1.0 0.0.0.255 any R1# show ip route 10.0.0.2
Routing entry for 10.0.0.2/32 Known via "ospf 1", distance 110, metric 20 Last update from 10.1.1.2 on GigabitEthernet0/1
Based on this output, what is the most likely problem?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-SET
R1# show route-map PBR-SET
route-map PBR-SET, permit, sequence 10 Match clauses:
ip address (access-lists): 160
Set clauses:
ip next-hop 192.168.1.2
ip tos 184Policy routing matches: 300 packets, 24000 bytes
R1# show access-lists 160
Extended IP access list 160
10 permit ip 10.0.0.0 0.255.255.255 any R1# show interfaces GigabitEthernet0/0
GigabitEthernet0/0 is up, line protocol is up Internet address is 10.0.0.1/24
Based on this output, a packet from source 10.0.0.5 to destination 8.8.8.8 arrives on GigabitEthernet0/0. What is the most likely behavior?
A network engineer runs the following command on Router R1:
R1# show ip policy Interface Route-map
GigabitEthernet0/0 PBR-TRACK
R1# show route-map PBR-TRACK
route-map PBR-TRACK, permit, sequence 10 Match clauses:
ip address (access-lists): 170
Set clauses:
ip next-hop verify-availability 10.0.0.2 10 track 2
Policy routing matches: 100 packets, 8000 bytes
R1# show track 2 Track 2 IP SLA 2 reachability
Reachability is Up 2 changes, last change 00:01:30 Latest operation return code: ok
Tracked by:
ROUTE-MAP 0
R1# show ip route 10.0.0.2
Routing entry for 10.0.0.2/32 Known via "eigrp 1", distance 90, metric 28160 Last update from 192.168.1.2 on GigabitEthernet0/1
Based on this output, what is the most likely behavior for packets matching ACL 170?
Router R1 has the following configuration:
```
interface GigabitEthernet0/1 ip address 10.1.1.1 255.255.255.0 ip policy route-map PBR-OUT
! route-map PBR-OUT permit 10 match ip address 100 set ip next-hop 192.168.1.1 !
access-list 100 permit ip host 10.1.1.100 any
``` What is the effect of this configuration?
Router R2 has the following configuration:
```
interface GigabitEthernet0/2 ip address 10.2.2.2 255.255.255.0 ip policy route-map CHECK
! route-map CHECK permit 10 match ip address 101 set interface GigabitEthernet0/3 !
access-list 101 permit tcp any any eq 80
``` What is the effect of this configuration?
Router R3 has the following configuration:
```
interface GigabitEthernet0/4 ip address 10.3.3.3 255.255.255.0 ip policy route-map PBR-IN
! route-map PBR-IN permit 10 match ip address 102 set ip next-hop verify-availability 192.168.2.1 10 track 1 !
access-list 102 permit ip 10.3.3.0 0.0.0.255 any
``` What is the effect of the 'set ip next-hop verify-availability' command?
Router R4 has the following configuration:
```
interface GigabitEthernet0/5 ip address 10.4.4.4 255.255.255.0 ip policy route-map PBR-DEFAULT
! route-map PBR-DEFAULT permit 10 set ip default next-hop 192.168.3.1 ``` What is the effect of this configuration?
Router R5 has the following configuration:
```
interface GigabitEthernet0/6 ip address 10.5.5.5 255.255.255.0 ip policy route-map PBR-METRIC
! route-map PBR-METRIC permit 10 match ip address 103 set metric 50 !
access-list 103 permit ip any any
``` What is the effect of the 'set metric 50' command in this PBR context?
Router R6 has the following configuration:
```
interface GigabitEthernet0/7 ip address 10.6.6.6 255.255.255.0 ip policy route-map PBR-MISS
! route-map PBR-MISS permit 10 match ip address 104 set ip next-hop 192.168.4.1 !
access-list 104 permit ip 10.6.6.0 0.0.0.255 192.168.0.0 0.0.255.255
``` What is missing in this configuration?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show route-map PBR-MAP
route-map PBR-MAP, permit, sequence 10 Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.1.1.2
ip next-hop verify-availabilityPolicy routing matches: 0 packets, 0 bytes
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show ip policy Interface Route-map
FastEthernet0/0 PBR-MAP
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# debug ip policy
Policy routing debugging is on R1#
*Mar 1 00:05:23.123: IP: s=192.168.1.10 (FastEthernet0/0), d=10.1.1.100, len 100, policy match *Mar 1 00:05:23.123: IP: s=192.168.1.10 (FastEthernet0/0), d=10.1.1.100, len 100, policy rejected
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show route-map PBR-MAP
route-map PBR-MAP, permit, sequence 10 Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.1.1.2
ip next-hop verify-availabilityPolicy routing matches: 100 packets, 12000 bytes
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# debug ip policy
Policy routing debugging is on R1#
*Mar 1 00:10:45.456: IP: s=172.16.1.5 (FastEthernet0/0), d=8.8.8.8, len 64, policy match *Mar 1 00:10:45.456: IP: s=172.16.1.5 (FastEthernet0/0), d=8.8.8.8, len 64, policy routed *Mar 1 00:10:45.456: IP: FastEthernet0/0 to Serial0/0 10.1.1.2
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show ip local policy Interface Route-map
local PBR-LOCAL
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show route-map PBR-MAP
route-map PBR-MAP, permit, sequence 10 Match clauses:
ip address (access-lists): 101
Set clauses:
ip next-hop 10.1.1.2
Policy routing matches: 50 packets, 6000 bytes
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# debug ip policy
Policy routing debugging is on R1#
*Mar 1 00:15:30.789: IP: s=10.0.0.1 (FastEthernet0/0), d=20.0.0.1, len 100, policy match *Mar 1 00:15:30.789: IP: s=10.0.0.1 (FastEthernet0/0), d=20.0.0.1, len 100, policy rejected *Mar 1 00:15:30.789: IP: s=10.0.0.2 (FastEthernet0/0), d=20.0.0.2, len 100, policy match *Mar 1 00:15:30.789: IP: s=10.0.0.2 (FastEthernet0/0), d=20.0.0.2, len 100, policy routed *Mar 1 00:15:30.789: IP: FastEthernet0/0 to GigabitEthernet0/1 192.168.1.1
What does this output indicate?
A network engineer runs the following command to troubleshoot a Policy-Based Routing (PBR) issue:
R1# show ip policy Interface Route-map
FastEthernet0/0 PBR-MAP Serial0/0 PBR-MAP
What does this output indicate?