SSH is a TCP-based service. A TCP monitor validates service availability without requiring application-layer inspection.

Connection rate limits restrict how many new connections are accepted per second, protecting application resources.

This scenario requires unequal load distribution based on server capacity. The newer servers must receive more connections than the older ones, while still dynamically accounting for active connection counts.
According to BIG-IP Administration: Data Plane Configuration documentation:
* Weighted Least Connections (member) combines:
* Connection awareness (least connections)
* Administrator-defined weights (ratios) to reflect server capacity
* Pool members with higher weights receive proportionally more new connections than members with lower weights, even when using the same load balancing algorithm.
Why B is correct:
* Allows assigning higher weights to newer servers and lower weights to older servers
* Ensures smarter traffic distribution based on both capacity and real-time load Why the other options are incorrect:
* A. Global AvailabilityUsed for disaster recovery and site failover, not intra-pool load distribution.
* C. Round RobinDistributes connections evenly without considering server capacity.
* D. Least Connections (member)Balances only by current connection count and does not account for differences in server performance or capacity.
Correct Resolution:
Use Weighted Least Connections (member) and assign higher weights to newer servers so they receive more traffic while protecting older servers from overload.

Standard BIG-IP administration dictates that hardware-level physical attributes are managed within the Network section of the configuration. When a network switch and a BIG-IP fail to successfully negotiate speed and duplex settings (Auto-Negotiation), it can result in CRC errors, late collisions, or a total lack of link. To resolve this manually, the administrator must navigate to the Configuration Utility (GUI) and go to Network > Interfaces.
Within the Interfaces list, the administrator can select the specific physical port (e.g., 1.1 or 1.2) and modify its properties. By default, the media speed is set to "Auto," but the drop-down menu allows for manual selection of specific speeds (e.g., 100Mb/s, 1Gb/s, 10Gb/s) and duplex settings (Full or Half). While these changes can also be made via the TMOS Shell (TMSH) (Option B) using the modify net interface command, the question asks for the standard location, which in most administrative contexts refers to the primary GUI path. System > Configuration (Option D) is used for global device settings like NTP, DNS, and licensing, not for interface-specific physical layer parameters. The Front Console (Option A), referring to the LCD panel on physical appliances, is primarily used for initial management IP setup and viewing system alerts, but does not provide the granular interface configuration required for media speed adjustments.

SSH (Secure Shell) operates over TCP port 22 , making the TCP health monitor the appropriate and correct choice for monitoring pool members in an SSH pool. The TCP monitor establishes a basic Layer 4 connection to each pool member on the designated port, verifying that the server is reachable and actively accepting TCP connections. A successful three-way handshake confirms the pool member is available; a failure marks it down and removes it from load balancing rotation.
The remaining monitor types are inappropriate for this use case:
* UDP monitor operates at Layer 4 but uses the connectionless UDP protocol, which is incompatible with SSH since SSH exclusively uses TCP as its transport.
* HTTP monitor sends a Layer 7 GET request expecting an HTTP response - irrelevant for an SSH service that does not speak the HTTP protocol.
* HTTPS monitor functions identically to HTTP but over TLS - again, completely misaligned with SSH traffic and port behaviour.
For application-specific SSH validation beyond basic TCP connectivity, an external monitor or custom monitor could be used; however, TCP remains the standard and correct built-in monitor for SSH pool verification within the BIG-IP platform.
Reference: BIG-IP Administration - Data Plane Configuration, Module: Health Monitors - Monitor Types and Protocol Alignment.