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

Cisco Exam 300-710 Topic 9 Question 108 Discussion

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

An engineer is troubleshooting a device that cannot connect to a web server. The connection is initiated from the Cisco FTD inside interface and attempting to reach 10.0.1.100 over the non-standard port of 9443 The host the engineer is attempting the connection from is at the IP address of 10.20.10.20. In order to determine what is happening to the packets on the network, the engineer decides to use the FTD packet capture tool Which capture configuration should be used to gather the information needed to troubleshoot this issue?

A)

B)

C)

D)

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Linwood
1 months ago
Option B is the way to go, just like my grandma used to say, 'Keep it simple, stupid' - or was that the CIA? Anyway, it works for this question too!
upvoted 0 times
Arlene
16 days ago
Option B is definitely the best choice here.
upvoted 0 times
...
...
Ronald
1 months ago
Option A, really? Who uses a packet capture tool to troubleshoot a web server connection issue? That's like using a sledgehammer to crack a nut.
upvoted 0 times
...
Becky
1 months ago
This is a tricky one, but I think Option D is the best bet. Capturing the traffic on both interfaces and using the advanced options to filter should give us a clear picture of what's happening.
upvoted 0 times
Ivette
3 days ago
I'm not sure, but Option A could be a good starting point to see if we can isolate the issue with the packet capture.
upvoted 0 times
...
Truman
8 days ago
I think Option C might also work well, as it focuses on capturing traffic specifically on the inside interface.
upvoted 0 times
...
Von
22 days ago
I agree, Option D seems like the most comprehensive choice for capturing the necessary information.
upvoted 0 times
...
...
Sueann
2 months ago
I see your point, but I think Option A would provide more detailed information for troubleshooting.
upvoted 0 times
...
Shoshana
2 months ago
I disagree, I believe Option C would be more appropriate in this scenario.
upvoted 0 times
...
Cary
2 months ago
I'm going with Option C. Capturing on the outside interface and filtering for the source IP and destination port sounds like the right approach.
upvoted 0 times
Augustine
7 days ago
Let's go with Option C then. It seems like the most efficient way to gather the necessary data for troubleshooting.
upvoted 0 times
...
Nilsa
14 days ago
Agreed, capturing on the outside interface and filtering for the specific source IP and destination port will give us the targeted information.
upvoted 0 times
...
Michell
1 months ago
I think Option C is the best choice too. It will help us filter the packets we need to troubleshoot.
upvoted 0 times
...
...
Glynda
2 months ago
Option B looks like the way to go. Capturing the traffic on the inside interface and filtering for the specific IP and port should give us the info we need.
upvoted 0 times
Marcos
28 days ago
Great, let's set up the packet capture using Option B and see if we can identify the problem with the connection.
upvoted 0 times
...
Jessenia
1 months ago
Let's go with Option B then, it should give us the information we need to figure out what's going on with the packets.
upvoted 0 times
...
Josephine
1 months ago
Yeah, filtering for the specific IP and port on the inside interface will help us troubleshoot the connection issue.
upvoted 0 times
...
Gilberto
1 months ago
I agree, Option B seems like the best choice for capturing the traffic we need.
upvoted 0 times
...
...
Sueann
2 months ago
I think we should use Option A for the packet capture.
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