CyberArk Remote Access enables privileged users and external vendors to establish controlled sessions through the Remote Access infrastructure.
In deployments containing multiple Remote Access Connector servers, load balancing improves service availability and distributes connection requests across available infrastructure.
However, file-transfer functionality within PSM sessions introduces additional session-state requirements.
For the Remote Access architecture described in this question, a standalone HTML5 Gateway must be deployed when file copying is required across multiple Connector servers.
The load balancer must also implement sticky sessions, sometimes referred to as session persistence.
Session persistence ensures that requests belonging to the same active privileged session continue reaching the appropriate Gateway instance.
Without consistent session routing, file-transfer operations may fail because subsequent requests can be forwarded to infrastructure that does not maintain the corresponding session context.
A standalone Gateway also separates HTML5 session processing from the Remote Access Connector deployment, improving architectural flexibility.
Round-robin distribution alone does not guarantee session persistence. Likewise, removing the HTML5 Gateway or relying directly on PSM does not provide the specified browser-based file-transfer capability.
Therefore, option A correctly combines the required Gateway deployment model and load-balancing behavior.
[Reference:CyberArk Remote Access — HTML5 Gateway Deployment, Standalone Gateway Architecture, Multiple Remote Access Connectors, Load-Balancer Session Persistence and PSM File Transfer., ]
Submit