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

CLIENT_DATA triggers when the BIG-IP system receives data from the client, which can be used for pool selection if the decision logic depends on initial data payloads not necessarily parsed as a full HTTP request yet.

SERVER_DATA triggers when the BIG-IP receives data from the server, which is generally too late for initial client-side pool selection decisions.

HTTP_REQUEST is a very common event for pool selection as it triggers when the BIG-IP system receives a complete HTTP request, allowing iRules to inspect HTTP headers or URIs for routing decisions before selecting a pool.

HTTP_RESPONSE triggers when the BIG-IP system receives a complete HTTP response from the server, which is after the pool has already been selected and the request forwarded.

CLIENT_ACCEPTED triggers when the BIG-IP system successfully establishes a client-side connection, making it suitable for early pool selection based on IP address, port, or other TCP/IP layer information, before any application-layer data is processed.

SERVER_SELECTED triggers after a server-side connection has already been selected or established, meaning the initial pool selection decision has already occurred.

SERVER_CONNECTED triggers when the BIG-IP establishes a server-side connection to a backend server, meaning the pool has already been chosen and the connection attempt is underway.