156-587 · Question #65
What is NOT a benefit of the 'fw ctl zdebug' command?
The correct answer is A. Cannot be used to debug additional modules. Option A is correct because fw ctl zdebug can in fact debug additional modules - you can pass flags like + drop or + all to target specific modules. The statement "cannot be used to debug additional modules" is simply false, making it the only choice that does not describe an…
Question
What is NOT a benefit of the 'fw ctl zdebug' command?
Options
- ACannot be used to debug additional modules
- BClean the buffer
- CCollect debug messages from the kernel
- DAutomatically allocate a 1MB buffer
How the community answered
(65 responses)- A86% (56)
- B8% (5)
- C5% (3)
- D2% (1)
Explanation
Option A is correct because fw ctl zdebug can in fact debug additional modules - you can pass flags like + drop or + all to target specific modules. The statement "cannot be used to debug additional modules" is simply false, making it the only choice that does not describe an actual benefit.
Options B, C, and D are all genuine capabilities of fw ctl zdebug: it does clean the debug buffer before collecting output (B), it does collect real-time debug messages directly from the Check Point kernel (C), and it does automatically allocate a 1MB buffer so you don't have to configure one manually (D).
Memory tip: Think of fw ctl zdebug as a "ready-to-go" debug tool - it handles buffer setup, buffer cleanup, and kernel message capture out of the box, and it's flexible enough to target additional modules. Any answer claiming it can't do something extra should raise a flag, since its whole purpose is broad kernel-level visibility.
Topics
Community Discussion
No community discussion yet for this question.