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.
[References:, CP_R81.20_Harmony_Endpoint_Server_AdminGuide.pdf, Page 25: "Optional Endpoint Security Elements" (EPS placement and role)., ]
