You need to run a kernel debug over a longer period of time as the problem occurs only once or twice a week. Therefore, you need to add a timestamp to the kernel debug and write the output to a file…

Question

Options

• Afw ctl debug -T -f -m 10 -s 1000000 -o debugfilename
• Bfw ctl kdebug -T -f -m 10 -s 1000000 > debugfilename
• Cfw ctl kdebug -T -f -m 10 -s 1000000 -o debugfilename
• Dfw ctl kdebug -T -m 10 -s 1000000 -o debugfilename

• A
  10% (6)
• B
  3% (2)
• C
  78% (46)
• D
  8% (5)

Explanation

Option C uses the correct command (fw ctl kdebug) with all required flags: -T for timestamps, -f to run in follow/foreground mode and write continuously to a file, -m 10 to set the buffer size, -s 1000000 to cap the file size and prevent filling your disk, and -o to properly specify the output filename as understood by the command itself.

Why the distractors fail:

• A uses fw ctl debug instead of fw ctl kdebug - the wrong base command entirely for kernel-level debugging
• B uses shell redirection (>) instead of -o, which does not integrate with the command's internal file-size limiting mechanism, defeating the purpose of -s
• D omits -f, which is the flag that enables continuous file writing mode - without it, output won't be saved to the file as intended

Memory tip: Think of the acronym "K-TF-SO" - Kdebug, Timestamp, Follow, Size-limit, Output - in that order, and remember that -o (not >) is the Check Point way to direct output so the size guard (-s) actually works.

No community discussion yet for this question.