Question

Options

• A$FWDIR/scripts/core-dump-enable.sh
• B

  set core-dump enable

• C

  set core-dump enable

• Dservice core-dump start

• B
  4% (1)
• C
  92% (22)
• D
  4% (1)

Explanation

Option C (> set core-dump enable) is the correct Gaia clish command for enabling core file creation on Check Point systems. The > symbol represents the Gaia clish (command-line shell) prompt, and the set core-dump enable syntax follows the standard clish pattern for toggling system features.

Why the distractors are wrong:

• A ($FWDIR/scripts/core-dump-enable.sh) - $FWDIR is a Check Point environment variable pointing to the firewall installation directory, but no such script exists for this purpose; it's a plausible-looking but fabricated path.
• B (# set core-dump enable) - The # prompt indicates expert mode (the underlying Linux root shell), not clish. The set core-dump enable syntax belongs to clish, not the expert shell, making this a mixed-context trap.
• D (service core-dump start) - This resembles a generic Linux SysV init command and is not valid syntax in either Gaia clish or Check Point's toolset.

Memory tip: Match the prompt to the shell - > means clish, # means expert mode. Since set commands are a clish convention, always pair set core-dump enable with the > prompt. Think: "greater-than = Gaia clish."

No community discussion yet for this question.