Which three iRule events are likely to be seen in iRules designed to select a pool for load balancing. (Choose 3)

CLIENT_DATA fires when raw data arrives from the client, allowing content-based pool selection before full protocol parsing, useful for non-HTTP protocols.

SERVER_DATA fires when data is received from the server, which occurs after a pool member has already been selected and connected.

HTTP_REQUEST fires after the HTTP request line and headers are parsed, giving access to URI, headers, and methods - the most common event for HTTP-based pool selection logic.

HTTP_RESPONSE fires when the server sends a response back to the client, which is well after pool selection has already been made.

CLIENT_ACCEPTED fires immediately when a TCP connection is established to the virtual server, allowing pool selection based on connection metadata like source IP or destination port before any data is exchanged.

SERVER_SELECTED fires after BIG-IP has already chosen a pool member, so it cannot be used to influence the pool selection decision.

SERVER_CONNECTED fires after the TCP connection to the chosen server is established, meaning pool selection has already occurred.