2V0-51-23 practice question 3 of 15

A new Horizon environment has gone into production. External sessions are being disconnected after a random period of time. The following information…

A new Horizon environment has gone into production. External sessions are being disconnected after a random period of time. The following information has been documented by the administrator: . Internal and external users are able to connect to their desktops. . External sessions connect via Unified Access Gateway. . Users are immediately able to reconnect but are disconnected again in a few minutes. . Due to limited amount of public IP addresses, all traffic flows through a load balancer. . Internal sessions, connected directly to the desktops, are not impacted. . While the session remains connected, all expected functionality works properly. What could be a cause of this issue?

Answer options

A: A misconfigured network load balancer is in front of the Unified Access Gateway appliances. Correct answer

B: A misconfigured network load balancer is in front of the Connection Servers.

C: Required firewall ports are not open in front of the Unified Access Gateway appliances.

D: Required firewall ports are not open in front of the Connection Servers.

Correct Answer:

A. A misconfigured network load balancer is in front of the Unified Access Gateway appliances.

Explanation

The symptoms described point directly to an issue with the load balancer situated in front of the Unified Access Gateway (UAG) appliances. External sessions disconnecting randomly, while internal sessions are stable, isolates the problem to the external access path (Client -> LB -> UAG). Such disconnects are classic symptoms of misconfigured session persistence (affinity) or incorrect UDP timeouts on the load balancer. The Blast Extreme protocol, for instance, uses multiple connections that must be routed to the same UAG appliance for the duration of the session. If the load balancer fails to maintain this affinity or has an aggressive UDP timeout, the session will break.

Why Incorrect

B. A misconfigured load balancer for Connection Servers would impact internal users as well, but the scenario states internal sessions are not impacted.
C. Blocked firewall ports would typically prevent the session from establishing at all or cause specific features to fail, not cause random disconnects of an active session.
D. Blocked firewall ports between UAG and Connection Servers would likely prevent authentication or desktop enumeration, stopping the connection before it starts.

References

1. VMware Docs (Unified Access Gateway 2209)

Deploying and Configuring VMware Unified Access Gateway

"Load Balancing Unified Access Gateway". This section states

"For Horizon

the load balancer must be configured for source IP affinity."

2. VMware Tech Zone

Load Balancing across VMware Unified Access Gateway Appliances

"Load Balancer Persistence". This operational tutorial details the requirement for source IP affinity for Horizon traffic to ensure a client is pinned to a specific UAG appliance.

3. VMware Docs (Unified Access Gateway 2209)

Deploying and Configuring VMware Unified Access Gateway

"Unified Access Gateway Firewall Rules". This shows that UDP timeouts are critical

stating "UDP timeout on the firewall must be a minimum of 30 seconds".

Keep practicing

Take the free 2V0-51-23 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test