156-115.80 · Question #122
What command would you use to view which debugs are set in your current working environment?
The correct answer is A. "env" and "fw ctl debug". Explanation/Reference:
Question
What command would you use to view which debugs are set in your current working environment?
Options
- A"env" and "fw ctl debug"
- B"cat /proc/etc"
- C"fw ctl debug all"
- D"export"
How the community answered
(33 responses)- A76% (25)
- B6% (2)
- C3% (1)
- D15% (5)
Explanation
Explanation/Reference:
Topics
Community Discussion
5
Lena V.Jun 26, 2026The correct answer is A, "env" and "fw ctl debug." On a Check Point gateway, "env" shows you all currently exported shell environment variables, which is where debug flags like TDERROR settings live, and "fw ctl debug" with no arguments (or used to inspect current state) shows you what kernel debug flags are active at the fw ctl level. You need both because Check Point debugging spans two layers, the user-space environment and the kernel module, and neither command alone gives you the full picture. Option C is a trap, "fw ctl debug all" sets all debug flags rather than displaying current ones, and options B and D are wrong because "cat /proc/etc" is not a valid path and "export" alone just lists exported shell vars without touching the fw ctl debug layer at all.
Fatima Z.Jun 29, 2026Solid breakdown, just pin this in your memory as the "EK combo" where E is env for user-space and K is kernel-side fw ctl debug, because when the exam tries to swap in "fw ctl debug all" as bait, remembering EK shows current state while "all" sets state will save you fast.
Fatima Z.Jun 15, 2026C tempts you but RESETS, not reads. Duo wins: env plus fw ctl debug.
Bao N.Jun 16, 2026Solid catch on the reset trap, and I would pile on that the env plus fw ctl debug combo only locks in once you have enough lab reps to see the counter behavior live, which is exactly why people who just read dumps still miss it under exam pressure.
Bao N.Jun 26, 2026That one catches people off guard because they assume you need a single dedicated command, but the real trick is knowing that env shows you environment variable debugs while fw ctl debug shows you kernel debug flags, so together they give you the full picture of what is active in your working environment. When you practiced this, did you find it more useful to run fw ctl debug with specific module flags to narrow things down, or do you typically just dump everything and filter?