Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-710 Topic 9 Question 98 Discussion

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

A network administrator is deploying a new Cisco Secure Firewall Threat Defense (FTD) firewall After Cisco Secure FTD is deployed, inside clients nave intermittent connectivity to each other. When ... the packet capture on the Secure FTD firewall, the administrator sees that Secure FID is responding to all the AW requests on the inside network. Which action must the network administrator e to resolve the issue''

Show Suggested Answer Hide Answer
Suggested Answer: A

If inside clients have intermittent connectivity issues and the Cisco Secure FTD is responding to all ARP requests on the inside network, it indicates that there may be an incorrect proxy ARP configuration in the NAT policy. Proxy ARP can cause the FTD to respond to ARP requests on behalf of other devices, leading to connectivity issues.

Steps to resolve:

Review the NAT policy on the FTD to identify any incorrect proxy ARP configurations.

Disable the proxy ARP setting for the relevant NAT rules that are causing the issue.

This ensures that the FTD only responds to ARP requests as needed, preventing it from interfering with normal ARP traffic on the inside network.


Contribute your Thoughts:

Vincent
2 months ago
Converting the FTD to transparent mode? Sounds like a recipe for disaster. I'm sticking with option C, my friend.
upvoted 0 times
Justine
29 days ago
Let's go with option C and see if that resolves the issue.
upvoted 0 times
...
Diego
1 months ago
I agree, reviewing the access policy seems like the safest bet.
upvoted 0 times
...
Carmelina
1 months ago
Option C sounds like the best solution to me.
upvoted 0 times
...
...
Sarina
3 months ago
Hardcoding MAC addresses? That's so 90s. I'd go with option A - review the NAT policy and disable that pesky proxy ARP.
upvoted 0 times
Lashanda
1 months ago
I think option A is the way to go. Let's make sure to review the NAT policy and fix that proxy ARP issue.
upvoted 0 times
...
Leonora
2 months ago
Yeah, hardcoding MAC addresses seems like a hassle. I agree, let's go with option A.
upvoted 0 times
...
Dalene
2 months ago
Option A sounds like the best solution. Let's review the NAT policy and disable the incorrect proxy ARP.
upvoted 0 times
...
...
Asha
3 months ago
I'm not sure, but I think option C) Review the access policy and verify that ARP is allowed from inside to inside could also be a valid solution.
upvoted 0 times
...
Alpha
3 months ago
Option C seems like the logical choice here. Gotta make sure that ARP is allowed from inside to inside on the access policy.
upvoted 0 times
...
Alexis
3 months ago
I agree with Herminia, because incorrect proxy ARP configuration can cause connectivity issues.
upvoted 0 times
...
Herminia
3 months ago
I think the answer is A) Review NAT policy and disable incorrect proxy ARP configuration.
upvoted 0 times
...
Shizue
3 months ago
Ah, the joys of firewall configuration! I bet the admin is having a blast trying to figure out this ARP issue.
upvoted 0 times
Avery
1 months ago
D: D) Convert the FTD to transparent mode to allow ARP requests.
upvoted 0 times
...
Carin
2 months ago
C: A) Review NAT policy and disable incorrect proxy ARP configuration.
upvoted 0 times
...
Barney
2 months ago
B: Hardcode the MAC address of the FTD to IP mapping on client machines.
upvoted 0 times
...
Whitley
2 months ago
B: C) Review the access policy and verify that ARP is allowed from inside to inside.
upvoted 0 times
...
Carin
2 months ago
A: A) Review NAT policy and disable incorrect proxy ARP configuration.
upvoted 0 times
...
Brinda
3 months ago
A: Review NAT policy and disable incorrect proxy ARP configuration.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77