Free 156-587 Exam Braindumps (page: 6)

Page 5 of 21

What is NOT a benefit of the `fw ctl zdebug' command?

  1. Automatically allocate a 1MB buffer
  2. Collect debug messages from the kernel
  3. Cannot be used to debug additional modules
  4. Clean the buffer

Answer(s): C



When debugging is enabled on firewall kernel module using the fw ctl debug' command with required options, many debug messages are provided by the kernel that help the administrator to identify

Issues.
Which of the following is true about these debug messages generated by the kernel module?

  1. Messages are written to /etc/dmesg file
  2. Messages are written to a buffer and collected using `fw ctl kdebug
  3. Messages are written to SFWDIR
  4. Messages are written to console and also /var/log/messages file

Answer(s): B



During firewall kernel debug with fw ctl zdebug you received less information that expected. You noticed that a lot of messages were lost since the time the debug was started.
What should you do to resolve this issue?

  1. Increase debug buffer Use fw ctl debug -buf 32768
  2. Redirect debug output to file; Use fw ctl debug -o /debug.elg
  3. Redirect debug output to file; Use fw ctl zdebug -o /debug.elg
  4. Increase debug buffer; Use fw ctl zdebug -buf 32768

Answer(s): A



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 but you cant afford to fill up all the remaining disk space and you only have 10 GB free for saving the debugs What is the correct syntax for this?

  1. A fw ctl kdebug -T -f -m 10 -s 1000000 -o debugfilename
  2. fw ctl debug -T -f-m 10 -s 1000000 -o debugfilename
  3. fw ctl kdebug -T -f -m 10 -s 1000000 > debugfilename
  4. fw ctl kdebug -T -m 10 -s 1000000 -o debugfilename

Answer(s): A






Post your Comments and Discuss Checkpoint 156-587 exam with other Community members: