201 · Question #310
Which three iRule events are likely to be seen in iRules designed to select a pool for load balancing? (Choose three.)
The correct answer is A. CLIENT_DATA C. HTTP_REQUEST E. CLIENT_ACCEPTED. Pool selection for load balancing typically occurs early in the connection lifecycle or after an HTTP request is fully received.
Question
Which three iRule events are likely to be seen in iRules designed to select a pool for load balancing? (Choose three.)
Options
- ACLIENT_DATA
- BSERVER_DATA
- CHTTP_REQUEST
- DHTTP_RESPONSE
- ECLIENT_ACCEPTED
- FSERVER_SELECTED
- GSERVER_CONNECTED
How the community answered
(30 responses)- A80% (24)
- D13% (4)
- F3% (1)
- G3% (1)
Why each option
Pool selection for load balancing typically occurs early in the connection lifecycle or after an HTTP request is fully received.
CLIENT_DATA is triggered when client data is received, allowing pool selection based on initial payload content before full application-layer parsing.
SERVER_DATA occurs when data is received from the backend server, which is too late for initial pool selection.
HTTP_REQUEST fires after the full HTTP request headers are received, enabling pool selection based on request details like URI, host, or headers.
HTTP_RESPONSE fires after the server's HTTP response is received, which is too late for initial pool selection.
CLIENT_ACCEPTED is triggered immediately upon client TCP connection establishment, permitting pool selection based on connection-level attributes such as source IP or port.
SERVER_SELECTED is triggered after a server from a pool has already been chosen, not as an event to initiate the selection logic itself.
SERVER_CONNECTED occurs after the connection to the backend server is established, which is too late for initial pool selection.
Concept tested: iRule events for pool selection
Source: https://techdocs.f5.com/en-us/bigip-15-0-0/big-ip-irules-reference/irule-events.html
Topics
Community Discussion
No community discussion yet for this question.