156-727.77 · Question #55
John is troubleshooting a dropped traffic issue. Looking in SmartViewTracker, he cannot find anything related to it. What CLI command might help him in this situation where he suspects a possible…
The correct answer is D. fw ctl zdebug drop. Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test…
Question
John is troubleshooting a dropped traffic issue. Looking in SmartViewTracker, he cannot find anything related to it. What CLI command might help him in this situation where he suspects a possible problem with IPS?
Options
- AAll of the information is visible in SmartViewTracker without additional commands.
- Bfw ctl pstat
- Cfw logexport ?grep drop
- Dfw ctl zdebug drop
How the community answered
(38 responses)- A5% (2)
- B13% (5)
- C3% (1)
- D79% (30)
Explanation
Exam Questions, Study Guides, Practice Tests. Lead the way to help you pass any IT Certification exams, 100% Pass Guaranteed or Full Refund. Especially Cisco, CompTIA, Citrix, EMC, HP, Oracle, VMware, Juniper, Check Point, LPI, Nortel, EXIN and so on. Our Slogan: First Test, First Pass. Help you to pass any IT Certification exams at the first try. You can reach us at any of the email addresses listed below. Any problems about IT certification or our products, you could rely upon us, we will give you satisfactory answers in 24 hours.
Topics
Community Discussion
5
Dervla O.Jun 25, 2026D is your answer, and the stem tells you exactly why if you read it twice: the traffic is dropped and SmartViewTracker shows nothing, which eliminates A on its own. SmartViewTracker only surfaces what the firewall actually logs, so a silent kernel-level drop, the kind IPS can cause, never makes it into that view at all. fw ctl zdebug drop works at the kernel level and catches those silent drops with their reasons, giving you visibility that the logging layer simply cannot provide. B gives you performance stats and C just exports the same logs you already know are empty, so both are dead ends the moment you accept that the standard log path is the problem.
Bao N.Jun 26, 2026The trap here is B, because pstat gives you statistics and it sounds diagnostic, but it tells you nothing about which specific packets are getting dropped or why. fw ctl zdebug drop is the right call, it streams real-time kernel drop notifications that SmartViewTracker never shows you, which is exactly what you need when IPS is silently eating traffic.
Ola B.Jun 11, 2026fw ctl zdebug drop is your go-to here because SmartViewTracker only shows what makes it into the log buffer, and IPS drops can happen in the kernel path before a log entry is ever written. Spin up a test environment and run that command while replaying the suspect traffic and you will see the drop reason printed in real time straight from the firewall kernel.
Hiroshi T.Jun 26, 2026pstat shows kernel stats including IPS counters, B is the right call here.
Dervla O.Jun 27, 2026Hiroshi, pstat is a BSD/legacy tool for process and swap stats, not the right fit here. D is correct because it targets the specific subsystem you need without the noise of broader system counters.