Refer to the exhibit.

An engineer recently implemented uRPF by configuring the ip verify unicast source reachable-via rx command on interface gi0/3 The engineer noticed right after implementing F that an inbound packet on the giO-3 interface with a source address of 172 16 3 251 was dropped. Which action resolves the issue?
Suggested Answer: A
Get Premium 300-410 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
28 comments · newest first
LI
Lindy
11 months ago
Agree, ACL adjustment seems like the best fix.
DA
Darrin
11 months ago
Surprised it dropped that packet! Thought it would be allowed.
CA
Casandra
11 months ago
I think loose mode could work here.
CA
Cassi
11 months ago
Definitely need to check the ACL for that IP.
JO
Johnson
12 months ago
uRPF strict mode drops packets not seen in the routing table.
SU
Susana
12 months ago
I vaguely recall that loose mode allows more flexibility, but I’m not confident if that’s the best option for this scenario.
QU
Quentin
1 year ago
I practiced a similar question, and I think uRPF strict mode would actually drop the packet too, so that's probably not the answer.
IS
Isabelle
1 year ago
I'm not entirely sure, but I feel like permitting the IP in the ACL could resolve the issue. It seems like a common practice question.
JE
Jennie
1 year ago
I remember studying uRPF and how it can drop packets if the source isn't reachable. I think loose mode might help here.
TE
Tenesha
1 year ago
I'm pretty confident that the right answer is to permit the 172.16.3.251 address in the inbound ACL. That should resolve the issue with the uRPF drop.
MI
Mitzie
1 year ago
Okay, the key here is that the packet was dropped due to the uRPF configuration. So I think the solution is to either configure uRPF loose mode or add the source address to the ACL.
DO
Dominic
1 year ago
Hmm, I'm a bit confused about the difference between uRPF loose and strict modes. I'll have to review that before deciding on the best answer.
AN
Anna
1 year ago
This looks like a tricky uRPF question. I'll need to carefully read through the options and think about how uRPF works.
SH
Shawna
1 year ago
I'm leaning towards option D - configuring uRPF strict mode. That seems like it would be the most secure approach to resolving the problem.
BR
Brandon
2 years ago
Hmm, that makes sense too. Let's see what others think before the exam.
KE
Keena
2 years ago
I disagree, I believe the correct answer is D) Configure uRPF strict mode to forward the packet.
TH
Theodora
2 years ago
Option A is the way to go, my friend. Loose mode will let the packet through, no problem.
AU
Augustine
2 years ago
D) Configure uRPF strict mode to forward the packet
JU
Junita
2 years ago
Got it, thanks for the advice!
DE
Devorah
2 years ago
B) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3.
TH
Theresia
2 years ago
A) Configure uRPF loose mode to forward the packet.
MO
Mohammad
2 years ago
Haha, I'm going to have to go with Option C. Gotta love those redundant answers that make you scratch your head!
DY
Dylan
2 years ago
I think Option B is the way to go. Permitting the source address in the ACL on the interface will allow the packet to pass through.
BR
Brandon
2 years ago
I think the answer is B) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3.
EL
Elmira
2 years ago
Option D makes the most sense. If the issue is that a packet with a source address of 172.16.3.251 is getting dropped, then we need to configure uRPF strict mode to forward the packet.
JA
Jacklyn
2 years ago
That should resolve the issue with the dropped packet.
VI
Viva
2 years ago
We should configure uRPF strict mode to forward the packet.
VE
Vernell
2 years ago
Option D makes the most sense.