Skip to main content
ITPrepCerts
Login
Exams Free Samples About Contact
Login Create an account

156-587 Check Point Certified Troubleshooting Expert - R81.20

  • Checkpoint
  • 5 free sample questions

About this exam

156-587 is the Checkpoint exam Check Point Certified Troubleshooting Expert - R81.20. Paid practice material for this exam is not available yet, but you can try its free sample questions.

Exam code
156-587
Vendor
Checkpoint
Practice questions
Not available yet
Free sample questions
5
Question bank last updated
Not available yet

Try 2 sample questions

Taken from the free sample set for 156-587.

Question 1

After kernel debug with “fw ctl debug you received a huge amount of information It was saved in a very large file that is difficult to open and analyze with standard text editors Suggest a solution to

solve this issue

  1. Option A:

    Reduce debug buffer to 1024KB and run debug for several times


  2. Option B:

    Use Check Point InfoView utility to analyze debug output


  3. Option C:

    Use “fw ctl zdebug because of 1024KB buffer size


  4. Option D:

    Divide debug information into smaller files. Use “ fw ctl kdebug -f -o “filename -m 25 - s ‘’1024’’

Show answer and explanation

Correct answer: D

 One possible solution to solve the issue of having a very large file that is difficult to open and analyze with standard text editors is to divide the debug information into smaller files. This can be done by using the  fw ctl kdebug  command with the  -f ,  -o ,  -m , and  -s  options. The  -f  option means to write the debug output to a file instead of the screen. The  -o  option specifies the name of the output file. The  -m  option sets the maximum number of files to be created. The  -s  option sets the maximum size of each file in KB. For example, the command  fw ctl kdebug -f -o debug -m 25 -s 1024  will create up to 25 files named debug.0, debug.1, …, debug.24, each with a maximum size of 1024KB. This way, the debug information can be split into more manageable chunks that can be opened and analyzed more easily with standard text editors.

[:, 1: How to use “fw ctl kdebug” command, 2: How to debug Check Point firewalls, 3: Check Point CLI Reference Card, , ]

Question 2

Which of the following commands can be used to see the list of processes monitored by the Watch Dog process?

  1. Option A:

    cpstat fw -f watchdog


  2. Option B:

    fw ctl get str watchdog


  3. Option C:

    cpwd_admin list


  4. Option D:

    ps -ef | grep watchd

Show answer and explanation

Correct answer: C

To see the list of processes monitored by the WatchDog process (CPWD), you use the cpwd_admin list command.

    Option A (cpstat fw -f watchdog) : Shows firewall status and statistics for the "fw" context, not necessarily the list of monitored processes.

    Option B (fw ctl get str watchdog) : Not a valid parameter for retrieving the list of monitored processes; “fw ctl” deals with kernel parameters.

    Option C (cpwd_admin list) : Correct command that lists all processes monitored by CPWD, their status, and how many times they have been restarted.

    Option D (ps -ef | grep watchd) : This will list any running process that matches the string “watchd” but will not specifically detail which processes are being monitored by CPWD.

Therefore, the best answer is cpwd_admin list .

Check Point Troubleshooting References

    sk97638 : Explains Check Point WatchDog (CPWD) usage and the cpwd_admin utility.

    R81.20 CLI Reference Guide : Describes common troubleshooting commands including cpwd_admin list.

    Check Point Gaia Administration Guide : Provides instructions for monitoring system processes and verifying CPWD.

See all 5 free sample questions