From the exhibit, the pool contains different applications on different service ports (for example, HTTP/80, FTP/21, HTTPS/443, SSH/22). To mark pool members correctly, BIG-IP must be able to verify the actual service running on each member’s port.
In BIG-IP Administration: Data Plane Configuration, monitor behavior is described as follows:
When multiple monitors are assigned to a pool, the Availability Requirement controls how monitor results are evaluated:
At least one = the pool member is marked up if any one of the assigned monitors succeeds.
All = the pool member is marked up only if every assigned monitor succeeds.
For pools containing members with different services/ports, using All can incorrectly mark members down because monitors intended for other services will fail on the wrong port.
Why C is correct:
Assigning HTTPS, HTTP, FTP, and SSH covers the actual services shown in the pool.
Setting the Availability Requirement to at least one ensures that each pool member is considered available when its appropriate service monitor succeeds, without being forced to pass unrelated service monitors.
Why the other options are incorrect:
A / D (Availability Requirement = all): would cause members to be marked down when unrelated monitors fail (e.g., SSH monitor against an HTTP member).
B (includes ICMP): ICMP can indicate the host is reachable even if the application service is down, which does not “accurately” reflect service availability.
Therefore, the best choice is HTTPS, HTTP, FTP, and SSH with Availability Requirement of at least one health monitor.
