Identify the Reason a Pool Member Has Been Marked Down by Health Monitors F5CAB5 Practice Questions (Page 3)

Questions 11–15

1. 11foundation · easy

   Which command-line tool can be used to view the health status of pool members in F5 BIG-IP?

   • Acurl
   • Bnetstat
   • Cping
   • Dtmsh
   Reveal Solution Discussion Select an answer first
2. 12application · medium

   An administrator is looking at the pool member status in the BIG-IP Configuration Utility. One member is showing a status of 'Unknown'. What does this status typically indicate?

   • AThe member is up and passing health checks.
   • BThe member has no health monitor associated with it, or the monitor has not yet run.
   • CThe member is in a transitional state after a single monitor failure.
   • DThe member is down and not accepting traffic.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   Which of the following is a type of health monitor used in F5 BIG-IP?

   • ASSL certificate monitor
   • BFirewall monitor
   • CHTTP monitor
   • DLoad balancer monitor
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A BIG-IP administrator has a pool with two members. A custom TCP monitor is assigned to the pool. The administrator notices that one member is marked down, but the other is up. The down member's application service is confirmed to be running and listening on the correct port. What is the most likely cause of this issue?

   • AThe monitor's timeout is set too high, causing it to wait too long for a response.
   • BThe down member has a firewall rule that is blocking the BIG-IP's source IP address.
   • CThe up member is on the same subnet as the BIG-IP, while the down member is on a different subnet.
   • DThe monitor is not associated with the pool, so it is not checking the members.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   An administrator has a pool with two members. A custom TCP monitor is assigned to the pool. One member is up, and the other is down. The down member is on a different subnet than the up member. The administrator can ping the down member from the BIG-IP. What is the most likely cause of the down state?

   • AThe monitor is not associated with the down member, so it is not being checked.
   • BThere is a firewall rule on the down member's subnet that is blocking the BIG-IP's source IP address.
   • CThe monitor's timeout is set too low, causing it to fail before the connection is established.
   • DThe monitor is configured with the wrong destination port for the down member.
   Reveal Solution Discussion Select an answer first