2V0-51.23 · Question #70
In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected. What happens if one of these Connection Servers runs into an unplanned outage?
The correct answer is D. Only the active sessions from the failed Connection Server are disconnected, because HTTPS. In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected. If one of these Connection Servers runs into an unplanned outage, only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure…
Question
In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected. What happens if one of these Connection Servers runs into an unplanned outage?
Options
- AAll 450 active sessions are disconnected, and have to re-connect again by the end-user.
- BAll active sessions will stay connected, because HTTPS Secure Tunnel and Blast Secure
- CAll 450 active session are logged off immediately.
- DOnly the active sessions from the failed Connection Server are disconnected, because HTTPS
How the community answered
(35 responses)- A9% (3)
- B3% (1)
- C3% (1)
- D86% (30)
Explanation
In a load balanced Horizon POD with three Connection Servers, there are 450 active Blast sessions connected. If one of these Connection Servers runs into an unplanned outage, only the active sessions from the failed Connection Server are disconnected, because HTTPS Secure Tunnel is disabled. This means that the other two Connection Servers can still handle the remaining sessions without interruption. The HTTPS Secure Tunnel is a feature that allows Horizon Client devices to establish secure connections to virtual desktops and applications through the Connection Server. When this feature is enabled, all the display protocol traffic is tunneled through the Connection Server, which acts as a proxy between the client and the desktop. This increases the security and simplifies the network configuration, but also adds some overhead and dependency on the Connection Server availability. When this feature is disabled, the Horizon Client devices connect directly to the desktops using their IP addresses or hostnames, bypassing the Connection Server. This reduces the load and dependency on the Connection Server, but also requires more network configuration and firewall rules to allow direct access to the desktops. The Blast Secure Gateway is a similar feature that allows Horizon Client devices to establish secure connections to virtual desktops and applications using the Blast Extreme protocol through the Connection Server. When this feature is enabled, the Blast Extreme traffic is tunneled through the Connection Server, which acts as a gateway between the client and the desktop. When this feature is disabled, the Horizon Client devices connect directly to the desktops using Blast Extreme. In this scenario, both HTTPS Secure Tunnel and Blast Secure Gateway are disabled, which means that the Horizon Client devices connect directly to the desktops using Blast Extreme. Therefore, if one of the Connection Servers fails, only the sessions that were authenticated by that Connection Server are affected. The other sessions can continue without interruption, as long as they can reach their desktops directly.
Topics
Community Discussion
No community discussion yet for this question.