156-587 · Question #69
What is the correct syntax to set all debug flags for Unified Policy related issues?
The correct answer is D. fw ctl debug -m UP all. Option D uses the correct command (fw ctl debug), the correct module name in its required uppercase form (UP for Unified Policy), and the correct flag (all) - making it the only syntactically valid choice for enabling all Unified Policy debug flags. Option A (fw ctl kdebug) is…
Question
What is the correct syntax to set all debug flags for Unified Policy related issues?
Options
- Afw ctl kdebug -m UP all
- Bfw ctl debug -m fw all
- Cfw ctl debug -m up all
- Dfw ctl debug -m UP all
How the community answered
(42 responses)- A5% (2)
- C2% (1)
- D93% (39)
Explanation
Option D uses the correct command (fw ctl debug), the correct module name in its required uppercase form (UP for Unified Policy), and the correct flag (all) - making it the only syntactically valid choice for enabling all Unified Policy debug flags.
Option A (fw ctl kdebug) is wrong because kdebug is not a valid subcommand; the correct one is debug.
Option B (-m fw) targets the fw (firewall kernel) module, not the Unified Policy module - a different debugging context entirely.
Option C (-m up) fails because the module name is case-sensitive on Check Point systems; lowercase up is not recognized as the Unified Policy module.
Memory tip: Think of it this way - "Unified Policy" is an important, capital concept, so its module flag is always written in CAPITALS: UP. If you remember that fw ctl debug -m <MODULE> all is the pattern, just keep UP uppercase and you'll never confuse it with option C.
Topics
Community Discussion
No community discussion yet for this question.