A Horizon administrator does not see the health status for the Unified Access Gateways (UAG) they configured in the Horizon Console. What two options could be causing the issue? (Choose two.)

The correct answer is A. The firewall hasn't been configured properly to allow traffic on port 443. B. The name entered in the Horizon console doesn't match up with the system name in UAG. If the Horizon Console does not display the health status of configured Unified Access Gateways (UAGs), it could be due to improper firewall configuration blocking traffic on port 443, which is essential for secure communication. Additionally, a discrepancy between the system…

Section 5 – Horizon Troubleshooting and Operations

Question

Options

AThe firewall hasn't been configured properly to allow traffic on port 443.
BThe name entered in the Horizon console doesn't match up with the system name in UAG.
CThe pod needs to be added to the Cloud Pod Federation.
DAnother license is needed for UAG health overview.
EThe Connection Server needs to be rebooted.

How the community answered

(38 responses)

A
76% (29)
C
8% (3)
D
3% (1)
E
13% (5)

Explanation

If the Horizon Console does not display the health status of configured Unified Access Gateways (UAGs), it could be due to improper firewall configuration blocking traffic on port 443, which is essential for secure communication. Additionally, a discrepancy between the system name in UAG and the name entered in the Horizon Console can also prevent the console from correctly retrieving and displaying the UAG's health status.

Topics

#Unified Access Gateway#UAG health status#firewall port 443#Horizon Console

Community Discussion

No community discussion yet for this question.

Full 2V0-51.23 Practice