CheckPoint Check Point Certified Harmony Endpoint Specialist - R81.20 156-536 Exam Practice Test

Answer : D

Push Operations allow the Endpoint Security Management Server to modify client settings, such as shutting down or restarting computers, without requiring a policy installation. This is detailed on page 69 under 'Performing Push Operations,' where the guide states that administrators can perform immediate actions like 'Restart Computer' and 'Shutdown Computer' on selected clients. Options like Remote Operations (A) and Node Management (B) are not documented features for this purpose, while Remote Help (C) is intended for user assistance, such as password recovery (page 425), not direct client modifications.

Answer : C

When troubleshooting errors related to Active Directory (AD) Strong Authentication in the Endpoint Security Management Server, the appropriate log file to examine is specified in the Check Point Harmony Endpoint Server Administration Guide R81.20. This guide provides detailed information on log file locations for various components of the Harmony Endpoint system.

On page 213, under the section 'Troubleshooting Authentication in Server Logs,' the guide explicitly states:

'The authentication logs are located in $UEPMDIR/logs/Authentication.log.'

This statement directly identifies $UEPMDIR/logs/Authentication.log as the correct location for logs related to authentication issues, including those involving AD Strong Authentication. The $UEPMDIR variable represents the installation directory of the Endpoint Security Management Server, making this path specific to the Harmony Endpoint environment. Therefore, Option C is the verified location for troubleshooting such errors.

To further validate this choice, consider the other options:

Option A: $FWDIR/log/Authentication.log -- The $FWDIR directory is typically associated with Check Point's firewall components (e.g., Security Gateway), not the Endpoint Security Management Server. This path is irrelevant for Harmony Endpoint authentication logs.

Option B: $FWDIR/logs/Auth.log -- Similarly, $FWDIR pertains to firewall-related logs, and 'Auth.log' is not a standard log file name in the Harmony Endpoint context, making this option incorrect.

Option D: $UEMPDlR/log/Authentication.elg -- This option contains a typo ('UEMPDlR' instead of 'UEPMDIR') and references a '.elg' file, which is typically used for debug logs in Check Point systems, not standard authentication logs. The correct extension, as per the guide, is '.log,' not '.elg.'

The documentation's clear directive on page 213 confirms that $UEPMDIR/logs/Authentication.log is the authoritative source for troubleshooting AD Strong Authentication issues, solidifying Option C as the correct answer.

CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 213: 'Troubleshooting Authentication in Server Logs' (location of authentication logs).

Answer : A

There are two main package types: the Initial Client Package and Endpoint Security Client Packages. Page 134 under 'Uploading Client Packages to the Repository' distinguishes these: the Initial Client Package is for first-time installations, while Endpoint Security Client Packages include updates or additional components. Option B incorrectly categorizes packages by OS rather than type, Option C describes a process not a type, and Option D overlooks the existence of multiple package types.

Answer : B

Answer : A

As detailed in the official Check Point Harmony Endpoint documentation, the Push Operation Wizard supports various push operations categorized specifically into Anti-Malware, Forensics and Remediation, and Agent Settings. These operations allow administrators to remotely manage security actions such as malware scans, forensic data collection, remediation tasks, and settings related to endpoint agents.

Exact Extract from Official Document:

'Push operations supported include Anti-Malware, Forensics and Remediation, and Agent Settings.'

Check Point Harmony Endpoint Specialist R81.20 Administration Guide.

Answer : B

Answer : B

Harmony Endpoint provides Endpoint Security Client packages for Windows, macOS, and Linux operating systems. This is explicitly documented in the CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf. On page 19, under the section 'Endpoint Security Client,' it states: 'The Endpoint Security client is available on Windows and Mac.' This confirms support for Windows and macOS. Further clarification is provided on page 51, under 'Supported Operating Systems for the Endpoint Client,' which lists 'macOS' and 'Linux' as supported platforms, alongside detailed support for Microsoft Windows on page 49. Together, these references confirm that the client packages are offered for Windows, macOS, and Linux.

Option A ('Unix, WinLinux and macOS') is incorrect because 'WinLinux' is not a recognized operating system, and Unix is not listed as a supported client OS in the documentation.

Option C ('macOS, iPadOS and Windows') is incorrect as iPadOS, an OS for mobile devices, is not mentioned as a supported platform for the Endpoint Security Client.

Option D ('Windows, AppleOS and Unix operating systems') is incorrect because 'AppleOS' is not a standard term (the correct term is macOS), and Unix is not supported as a client OS.

Thus, Option B is the only fully accurate choice based on the official documentation.

CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 19: 'Endpoint Security Client' (mentions Windows and Mac).

CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 49: 'Microsoft Windows' (details Windows support).

CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 51: 'macOS' and 'Linux' (confirms support for these OSes).