Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Cisco 300-410 Exam - Topic 15 Question 98 Discussion

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?
A) Configure uRPF loose mode to forward the packet.
B) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3.
C) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3 to allow 172.16.3.251.
D) Configure uRPF strict mode to forward the packet

Cisco 300-410 Exam - Topic 15 Question 98 Discussion

Actual exam question for Cisco's 300-410 exam
Question #: 98
Topic #: 15
[All 300-410 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

Option A configures uRPF loose mode to forward the packet. This mode allows the router to check if there is a route in the routing table that matches the source IP address of the incoming packet, regardless of the interface that is used to reach the source.This mode is suitable for networks that have asymmetric routing, where the incoming and outgoing interfaces for a packet may differ2.

Option B permits the 172.16.3.251 in the inbound ACL on interface gi0/3. This option does not resolve the issue, because it only allows the packet to pass the ACL check, but not the uRPF check.The packet will still be dropped by uRPF if there is no route to reach the source IP address via the same interface3.

Option C permits the 172.16.3.251 in the inbound ACL on interface gi0/3 to allow 172.16.3.251. This option is redundant and incorrect, because it repeats the same IP address twice in the ACL statement.It also does not resolve the issue for the same reason as Option B3.

Option D configures uRPF strict mode to forward the packet. This option does not resolve the issue, because it is the same mode that was already configured on the interface. Strict mode requires that the router has a route to reach the source IP address via the same interface where the packet was received.If this condition is not met, the packet will be dropped4.


by Tegan at Sep 15, 2024, 08:25 PM

Limited Time Offer

25%

Off

Get Premium 300-410 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lindy
9 months ago
Agree, ACL adjustment seems like the best fix.
upvoted 0 times
...
Darrin
9 months ago
Surprised it dropped that packet! Thought it would be allowed.
upvoted 0 times
...
Casandra
10 months ago
I think loose mode could work here.
upvoted 0 times
...
Cassi
10 months ago
Definitely need to check the ACL for that IP.
upvoted 0 times
...
Johnson
10 months ago
uRPF strict mode drops packets not seen in the routing table.
upvoted 0 times
...
Susana
10 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.
upvoted 0 times
...
Quentin
11 months 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.
upvoted 0 times
...
Isabelle
11 months 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.
upvoted 0 times
...
Jennie
11 months ago
I remember studying uRPF and how it can drop packets if the source isn't reachable. I think loose mode might help here.
upvoted 0 times
...
Tenesha
11 months 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.
upvoted 0 times
...
Mitzie
11 months 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.
upvoted 0 times
...
Dominic
11 months 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.
upvoted 0 times
...
Anna
11 months ago
This looks like a tricky uRPF question. I'll need to carefully read through the options and think about how uRPF works.
upvoted 0 times
...
Shawna
11 months 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.
upvoted 0 times
...
Brandon
2 years ago
Hmm, that makes sense too. Let's see what others think before the exam.
upvoted 0 times
...
Keena
2 years ago
I disagree, I believe the correct answer is D) Configure uRPF strict mode to forward the packet.
upvoted 0 times
...
Theodora
2 years ago
Option A is the way to go, my friend. Loose mode will let the packet through, no problem.
upvoted 0 times
Augustine
2 years ago
D) Configure uRPF strict mode to forward the packet
upvoted 0 times
...
Junita
2 years ago
Got it, thanks for the advice!
upvoted 0 times
...
Devorah
2 years ago
B) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3.
upvoted 0 times
...
Theresia
2 years ago
A) Configure uRPF loose mode to forward the packet.
upvoted 0 times
...
...
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!
upvoted 0 times
...
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.
upvoted 0 times
...
Brandon
2 years ago
I think the answer is B) Permit the 172.16.3.251 in the inbound ACL on interface gi0/3.
upvoted 0 times
...
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.
upvoted 0 times
Jacklyn
2 years ago
That should resolve the issue with the dropped packet.
upvoted 0 times
...
Viva
2 years ago
We should configure uRPF strict mode to forward the packet.
upvoted 0 times
...
Vernell
2 years ago
Option D makes the most sense.
upvoted 0 times
...
...

Save Cancel