Refer to the exhibit. A BIG-IP Administrator creates a new Virtual Server to load balance SSH traffic. Users are unable to log on to the servers. What should the BIG-IP Administrator do to resolve…

SSH operates over TCP, not UDP; setting the protocol to UDP would prevent all SSH connections from establishing correctly.

SSH is a TCP-based protocol, not HTTP. Applying an HTTP profile to an SSH virtual server causes the BIG-IP system to attempt HTTP processing and parsing, which interferes with the SSH handshake and prevents successful user logins, thus setting the HTTP profile to 'None' bypasses this Layer 7 processing.

Setting the source address to a specific IP would restrict access from only that IP and does not resolve issues related to protocol interference from an HTTP profile.

Setting the destination addresses/mask to 0.0.0.0/0 is a common wildcard configuration for a virtual server but does not address issues caused by an incorrect profile assignment for the traffic type.