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…

The exhibit shows a Virtual Server configured with an HTTP profile, but the intended traffic is SSH. An HTTP profile instructs the BIG-IP system to parse traffic according to RFC standards for HTTP. When non-HTTP traffic like SSH is sent to this virtual server, the system cannot parse it, leading to a connection reset. To allow raw TCP traffic like SSH to pass through correctly, the HTTP profile must be removed by setting it to 'None'.

A. Set Protocol to UDP: SSH is a TCP-based protocol, not UDP. Changing the protocol to UDP would prevent any TCP-based SSH connection from being established.

C. Set Source Address to 10.1.1.2: This would restrict access to a single source IP address and does not address the underlying protocol-level incompatibility causing the failure.

D. Set Destination Addresses/Mask to 0.0.0.0/0: This changes the virtual server to a wildcard listener, which is not the issue. The problem is the incorrect profile handling the traffic.

1. F5 Networks. (2021). BIG-IP LTM: Implementations - Chapter 3: F5 LTM Profiles. F5 Support (AskF5), K00809333. (This guide explains that profiles must match the type of traffic being processed.)

2. F5 Networks. (2023). About Virtual Servers. BIG-IP Local Traffic Manager: Concepts, 17.1.x. F5 Cloud Docs. (Section: "Virtual server components," which details the function of profiles.)

3. F5 Networks. (2017). SOL14783: The BIG-IP LTM system may drop or reset connections that do not match the virtual server's protocol profile. F5 Support (AskF5), K14783. (This article explicitly describes connection failures when traffic does not match the applied profile.)