101 · Question #70
Why would an administrator capture monitor traffic between a BIG-IP and servers?
The correct answer is A. Viewing monitor traffic could help the administrator to define a more robust monitor.. This question tests understanding of why an administrator would capture and analyze BIG-IP health monitor traffic.
Question
Why would an administrator capture monitor traffic between a BIG-IP and servers?
Options
- AViewing monitor traffic could help the administrator to define a more robust monitor.
- BIf a client were having difficulty logging into a loadbalanced SSH server, viewing and analyzing
- COnly client traffic may be captured; monitor traffic may not be captured.
- DIf client traffic to servers was failing, viewing and analyzing monitor traffic would determine the
How the community answered
(18 responses)- A94% (17)
- C6% (1)
Why each option
This question tests understanding of why an administrator would capture and analyze BIG-IP health monitor traffic.
Capturing monitor traffic using a tool like tcpdump allows an administrator to see exactly what the BIG-IP sends and what the server responds with during a health check. This visibility is valuable for diagnosing why monitors are marking servers down and for refining monitor send/receive strings or intervals. A more accurate monitor reduces false positives and improves pool availability.
Client SSH login issues are diagnosable via client-side traffic capture, not monitor traffic, since monitor probes and client sessions are separate flows.
Monitor traffic can be captured on BIG-IP using standard packet capture tools like tcpdump on the relevant VLAN interface.
Monitor traffic only shows whether the health check itself is passing or failing, not the root cause of client traffic failures, which requires capturing actual client-to-server flows.
Concept tested: BIG-IP health monitor traffic capture and analysis
Source: https://support.f5.com/csp/article/K13637
Topics
Community Discussion
No community discussion yet for this question.