Checkpoint 156-587 Exam
Check Point Certified Troubleshooting Expert - R81.20 (Page 6 )

Updated On: 7-Feb-2026

Where will the usermode core files located?

  1. $FWDIRVar/log/dump/usermode
  2. /var/suroot
  3. /var/log/dump/usermode
  4. $CPDIR/var/log/dump/usermode

Answer(s): D

Explanation:

Usermode core files are generated when a user mode process crashes. They are located in the $CPDIR/var/log/dump/usermode directory on the Security Gateway or Security Management server. The core files can be used to analyze the cause of the crash and troubleshoot the issue. The core files are named according to the process name, date, and time of the crash. For example, cpd_2023_02_03_16_40_55.core is a core file for the cpd process that crashed on February 3, 2023 at 16:40:55



What is the function of the Core Dump Manager utility?

  1. To determine which process is slowing down the system
  2. To send crash information to an external analyzer
  3. To limit the number of core dump files per process as well as the total amount of disk space used by core files
  4. To generate a new core dump for analysis

Answer(s): C

Explanation:

The Core Dump Manager (CDM) is a utility that helps manage core dump files on Check Point systems. Its main functions include:

Limiting file size and number: CDM can be configured to limit the size of individual core dump files and the total amount of disk space used for core dumps. This prevents core dumps from filling up valuable disk space.

Compression: CDM can compress core dump files to reduce their storage size. This is particularly helpful when dealing with large core dumps.

Process filtering: CDM allows you to specify which processes should be allowed to generate core dumps. This can help prevent unnecessary core dumps from being created.

Remote collection: CDM can be configured to send core dump files to a remote server for analysis.

This is useful in environments where direct access to the system generating the core dump is limited.

By using CDM, you can effectively manage core dump files and ensure that they are not overwhelming your system's resources.



What is the proper command for allowing the system to create core files?

  1. service core-dump start
  2. SFWDIR/scripts/core-dump-enable.sh
  3. set core-dump enable
    >save config
  4. # set core-dump enable
    # save config

Answer(s): C



When a user space process or program suddenly crashes, what type of file is created for analysis

  1. core dump
  2. kernel_memory_dump dbg
  3. core analyzer
  4. coredebug

Answer(s): A

Explanation:

When a user space process crashes unexpectedly, the operating system often creates a core dump file. This file is a snapshot of the process's memory at the time of the crash, including information such as:

Program counter: This indicates where the program was executing when it crashed.

Stack pointer: This shows the function call stack, which can help trace the sequence of events leading to the crash.

Memory contents: This includes the values of variables and data structures used by the process.

Register values: This shows the state of the processor registers at the time of the crash.

Core dump files can be analyzed using debuggers like GDB to understand the cause of the crash.

Why other options are incorrect:

B . kernel_memory_dump dbg: This refers to a kernel memory dump, which is generated when the operating system kernel itself crashes.

C . core analyzer: This is a tool used to analyze core dump files, not the file itself.

D . coredebug: This is not a standard term for any type of crash dump file.

Check Point Troubleshooting


Reference:

Check Point's documentation mentions core dumps in the context of troubleshooting various processes, such as fwd (firewall) and cpd (Check Point daemon). You can find information on enabling core dumps and analyzing them in the Check Point administration guides and knowledge base articles.



You receive reports from multiple users that they cannot browse Upon further discovery you identify that Identity Awareness cannot identify the users properly and apply the configuredAccess Roles

What commands you can use to troubleshoot all identity collectors and identity providers from the command line?

  1. on the gateway: pdp debug set IDC all IDP all
  2. on the gateway: pdp debug set AD all and IDC all
  3. on the management: pdp debug on IDC all
  4. on the management: pdp debug set all

Answer(s): A

Explanation:

To troubleshoot Identity Awareness issues related to user identification and Access Role application, you need to enable debugging for both Identity Collectors (IDC) and Identity Providers (IDP). The command pdp debug set IDC all IDP all on the gateway achieves this.

Here's why this is the correct answer and why the others are not:

A . on the gateway: pdp debug set IDC all IDP all: This correctly enables debugging for all Identity Collectors and Identity Providers, allowing you to see detailed logs and messages related to user identification and Access Role assignment. This helps pinpoint issues with user mapping, authentication, or authorization.

B . on the gateway: pdp debug set AD all and IDC all: This command only enables debugging for Active Directory (AD) as an Identity Provider and all Identity Collectors. It might miss issues related to other Identity Providers if they are in use.

C . on the management: pdp debug on IDC all: This command has two issues. First, it should be executed on the gateway, not the management server, as the gateway is responsible for user identification and policy enforcement. Second, it only enables debugging for Identity Collectors, not Identity Providers.

D . on the management: pdp debug set all: While this command might seem to enable debugging for everything, it's not specific enough for Identity Awareness troubleshooting. It might generate excessive logs unrelated to the issue and make it harder to find the relevant information.

Check Point Troubleshooting


Reference:

Check Point Identity Awareness Administration Guide: This guide provides detailed information about Identity Awareness components, configuration, and troubleshooting.

Check Point sk113963: This article explains how to troubleshoot Identity Awareness issues using debug commands and logs.

Check Point R81.20 Security Administration Guide: This guide covers general troubleshooting and debugging techniques, including the use of pdp debug commands.



Viewing page 6 of 23
Viewing questions 26 - 30 out of 109 questions



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

Join the 156-587 Discussion