201 · Question #155
A BIG-IP Administrator is configuring an SSH Pool with five members. Which Health Monitor should be applied to ensure that available pool members are monitored accordingly?
The correct answer is D. tcp. For an SSH pool, a TCP health monitor should be applied to ensure basic connectivity and availability of the SSH service on pool members.
Question
A BIG-IP Administrator is configuring an SSH Pool with five members. Which Health Monitor should be applied to ensure that available pool members are monitored accordingly?
Options
- Ahttps
- Budp
- Chttp
- Dtcp
How the community answered
(47 responses)- A2% (1)
- C4% (2)
- D94% (44)
Why each option
For an SSH pool, a TCP health monitor should be applied to ensure basic connectivity and availability of the SSH service on pool members.
An HTTPS health monitor is used for web services secured with SSL/TLS, typically on port 443, which is not applicable for a standard SSH service.
A UDP health monitor is designed for connectionless services that utilize the UDP protocol, whereas SSH operates over TCP.
An HTTP health monitor is specifically for web services, typically on port 80, and would not correctly assess the health of an SSH service.
An SSH service operates over TCP port 22, so a TCP health monitor is the appropriate choice to verify if the port is open and the underlying TCP stack is responsive on the pool member.
Concept tested: F5 BIG-IP health monitors for SSH
Source: https://techdocs.f5.com/en-us/bigip-16-0-0/big-ip-system-health-monitors/about-health-monitors.html
Topics
Community Discussion
No community discussion yet for this question.