HTTP pool attached to a Virtual Server has three members Pool member. - A default HTTP monitor in red - Pool member 6 custom HTTP monitor in green - Pool member C does not monitor Which pool members p

Pool member A has a red (failed) monitor and is marked down, so it is excluded from load balancing despite pool member C being included.

Pool member A cannot participate because its default HTTP monitor is red, indicating the health check is failing and BIG-IP has removed it from the active pool.

Pool member B has a green custom HTTP monitor, meaning it is passing health checks and is active in the load balancing pool. Pool member C has no monitor assigned, so BIG-IP treats it as always up by default and includes it in load balancing. Pool member A has a red (failed) monitor, so BIG-IP marks it down and excludes it from receiving traffic.

Pool member C participates because a missing monitor defaults to always-up status, and pool member A is excluded due to its failed red monitor.