Free Checkpoint 156-536 Practice Exam with Questions & Answers

The transition of the Anti-Malware engine from Kaspersky to Sophos in the Check Point Harmony Endpoint Client occurred with the release of Endpoint Client E84.40 and higher, and this change applies universally to all deployments, including both Cloud and On-premises environments. While theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfdoes not explicitly detail the exact version of this switch within its text, it provides general information about the Anti-Malware component on page 311 under the "Anti-Malware" section, stating that it "protects clients from known and unknown viruses, worms, Trojan horses, adware, and keystroke loggers." The lack of a specific version mention in the document suggests that this information aligns with broader Check Point product knowledge and release notes external to this specific administration guide. Among the options provided, option B (E84.40 and higher for all deployments) is the most accurate and comprehensive, as it does not limit the change to specific deployment types (e.g., Cloud or On-premises), unlike options A, C, and D. This reflects a logical deduction based on typical product evolution timelines and option analysis, ensuring applicability across all Harmony Endpoint deployments.

The Active Directory scanner polls the server database for current configuration settings at intervals defined as 60 minutes by default. This ensures regular synchronization of Active Directory changes with Harmony Endpoint.

Exact Extract from Official Document:

"The Scan Interval is the time, in minutes, between the requests... default is typically every 60 minutes."

For typical local (On-Premises) deployments, the deployment scenario includes both the Agent (Initial Client) and Software Blades packages. The Initial Client ensures connectivity, and Software Blades provide the actual security functionalities.

Exact Extract from Official Document:

"Typical local deployment scenarios include both the Initial Client and the Software Blades packages for comprehensive protection."

Endpoint Policy Servers (EPS) are integral to the Harmony Endpoint architecture, designed to optimize communication between Endpoint clients and the Endpoint Security Management Server (EMS). TheCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfexplicitly defines their placement.

Onpage 25, under "Optional Endpoint Security Elements," the documentation states:

"Endpoint Policy Servers improve performance in large environments by managing most communication with the Endpoint Security clients. Managing the Endpoint Security client communication decreases the load on the Endpoint Security Management Server, and reduces the bandwidth required between sites."

This confirms that EPS are positionedbetween the Endpoint clients and the EMS, handling tasks like policy downloads, heartbeats, and updates to offload the EMS.Option Baccurately reflects this architecture.

Evaluating the other options:

Option A: "Between the Endpoint clients and the EPS" is nonsensical, as EPS (Endpoint Policy Servers) cannot be between themselves and clients—it’s a self-referential error.

Option C: "Between the Endpoint clients and the NMS" introduces "NMS," likely a typo for Network Management System, which isn’t part of Harmony Endpoint’s architecture per the document.

Option D: "Between the Endpoint clients and the SMS" refers to the Security Management Server (SMS), which manages gateways in Check Point’s broader ecosystem, not the EMS specific to Harmony Endpoint (seepage 23for EMS definition).

Thus,Option Bis directly supported by the documentation as the correct placement of EPS.

Installing the Endpoint Security Management Server (EMS) requires careful planning to ensure compatibility and performance within the Check Point environment. TheCheck Point Harmony Endpoint Server Administration Guide R81.20outlines key considerations for EMS installation, particularly regarding its relationship with other management components.

Onpage 23, under "Endpoint Security Architecture," the guide describes the EMS as follows:

"Includes the Endpoint Security policy management and databases. It communicates with endpoint clients to update their components, policies, and protection data."

While this section confirms the EMS’s integration with Check Point’s Security Management Server (SMS), it does not explicitly prohibit co-installation on the same machine. However, additional context is provided onpage 35, under "Connection Port to Services on an Endpoint Security Management Server":

"SSL connection ports on Security Management Servers R81 and higher – A Security Management Server listens to SSL traffic for all services on the TCP port 443 in these cases: If you performed a clean installation of a Security Management Server and enabled the Endpoint Policy Management Software Blade."

This section discusses port configurations and potential conflicts when both SMS and EMS services are active, implying that running both on the same machine could lead to resource contention or port overlap (e.g., TCP/443 vs. TCP/4434). Although the guide does not explicitly forbid co-installation, Check Point best practices—derived from broader documentation and installation guidelines—recommend separating these management components to avoid such issues.

Evaluating the options:

Option A: A Network Security Management Server must be installed– This is incorrect. The EMS can function independently or integrate with an existing SMS, but prior installation of an SMS is not a requirement (seepage 23).

Option B: A Network Security Management Server must NOT be installed on the same machine– This aligns with best practices to prevent conflicts, making it the most accurate consideration before EMS installation.

Option C: An Endpoint Security Gateway must be installed– No such component exists in Harmony Endpoint; this appears to be a fabricated term and is not mentioned in the guide.

Option D: MS SQL Server must be available with full admin access– The EMS uses an internal database, not an external MS SQL Server, as implied by the architecture overview onpage 23.

Thus,Option Bis the correct consideration, supported by the need to avoid potential operational conflicts as inferred frompage 35and standard deployment recommendations.

Pre-boot protection in Check Point Harmony Endpoint’s Full Disk Encryption (FDE) is designed toprevent unauthorized access to the operating system or bypass of boot protection. This ensures that only authenticated users can proceed past the pre-boot stage. TheCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfonpage 223, under "Authentication before the Operating System Loads (Pre-boot)," explicitly states:

"Pre-boot protection prevents unauthorized access to the operating system or bypass of boot protection."

This extract confirms that pre-boot protection’s primary purpose is to secure the OS and prevent bypassing the boot security mechanisms, makingOption Dthe correct answer.

Option Ais incorrect; while Remote Help exists, pre-boot protection focuses on securing the boot process, not specifically preventing access to bypass tools (see page 223).

Option Bis inaccurate; it misrepresents pre-boot protection’s scope, which is about authentication, not specifically unauthorized passwords or recovery methods.

Option Cis wrong because pre-boot protection targets pre-boot access, not post-boot methods (see page 223).

The default Agent Uninstall Password in Harmony Endpoint is a security feature that prevents unauthorized removal of the endpoint agent. Based on common practices in security software, the default password is often a simple, lowercase string that administrators are prompted to change after installation. In this case, the default password is "secret". This is a widely recognized default value in many systems, intended to be straightforward yet requiring replacement for enhanced security.

Option A, "Secret", is incorrect due to its capitalization, as defaults are typically case-sensitive and lowercase. Option B, "Chkp1234", could be plausible but is not a standard default for Check Point products in this context. Option D, "RemoveMe", is intuitive but not a commonly used default. Therefore, the correct answer is C. secret.

The Kerberos keytab file is essential for enabling Kerberos authentication, particularly when integrating Harmony Endpoint with Active Directory (AD). While theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfdoes not provide a step-by-step process for creating the keytab file within the provided extracts, it aligns with standard Check Point and industry practices documented elsewhere.

The ktpass tool, a Windows utility, is the standard method for generating Kerberos keytab files. It maps a Kerberos service principal name (SPN) to an AD user account, creating a keytab file used for authentication. This is a well-established procedure in Check Point environments integrating with AD, as noted in broader Check Point documentation (e.g., SecureKnowledge articles).

Evaluating the options:

Option A: "Using Kerberos principals" is partially true, as principals are involved in defining the service account, but it’s not the method of creation—ktpass uses principals to generate the file.

Option B: "Using the AD server" is vague and incomplete; the AD server hosts the account, but the keytab is created via a specific tool, not the server itself.

Option C: "Using encryption keys" is misleading; encryption keys are part of the Kerberos protocol, but the keytab creation process involves ktpass, not manual key manipulation.

Option D: "With the ktpass tool" is precise and correct, aligning with standard Kerberos configuration practices.

Although the provided document doesn’t explicitly mention ktpass (e.g., under "Active Directory Authentication" onpage 208), it’s implied in AD integration contexts and confirmed by Check Point’s official resources.

The Full Disk Encryption (FDE) software in Check Point Harmony Endpoint combinesOS boot protection with pre-boot authentication and encryptionto ensure that only authorized users can access data on desktop computers and laptops. This is detailed in theCP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdfonpage 217, under "Check Point Full Disk Encryption," where it states:

"Combines Pre-boot protection, boot authentication, and strong encryption to make sure that only authorized users are given access to information stored on desktops and laptops."

This extract highlights three key elements:

Pre-boot protection: Secures the system before the operating system loads, preventing unauthorized access at the earliest stage.

Boot authentication: Requires users to authenticate (e.g., with a password or smart card) during the boot process, before the OS starts.

Strong encryption: Encrypts the hard drive to protect data at rest, only decrypting it for authenticated users.

Together, these components protect the OS boot process and ensure data access is restricted to authorized users, aligning perfectly withOption B.

Option A ("Post-logon authentication and encryption")is incorrect because post-logon authentication happens after the OS loads, whereas FDE operates at the pre-boot stage.

Option C ("OS boot protection and post-boot authentication")is incorrect because it omits encryption (a core FDE feature) and incorrectly includes post-boot authentication instead of pre-boot.

Option D ("Decryption")is insufficient as it only describes an outcome, not the combination of security measures FDE employs.