Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

F5 Networks F5CAB2 Exam - Topic 1 Question 10 Discussion

Which three iRule events are likely to be seen in iRules designed to select a pool for load balancing? (Choose three.)
A) CLIENT_DATA and C) HTTP_REQUEST and E) CLIENT_ACCEPTED
B) SERVER_DATA
D) HTTP_RESPONSE
F) SERVER_SELECTED
G) SERVER_CONNECTED

F5 Networks F5CAB2 Exam - Topic 1 Question 10 Discussion

Actual exam question for F5 Networks's F5CAB2 exam
Question #: 10
Topic #: 1
[All F5CAB2 Questions]

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

Show Suggested Answer Hide Answer
Suggested Answer: A, C, E

12

In the BIG-IP system, pool selection must occur on the client-side of the connection, before the system attempts to connect to a pool 3member. The events listed 4are the primary entry points for making these decisions:

CLIENT_ACCEPTED (E): This is a Layer 4 event triggered when the BIG-IP accepts a TCP connection. It is the earliest point where a pool can be assigned based on the client's source IP address or the destination port.

CLIENT_DATA (A): This event is triggered when the system receives a 'chunk' of data on the client-side. It is often used for non-HTTP protocols (like custom TCP protocols) to inspect the payload and select a pool based on its contents.

HTTP_REQUEST (C): This is a Layer 7 event. It occurs once the BIG-IP has fully parsed the HTTP headers. This is the most common event for pool selection, allowing the administrator to route traffic based on the URI, Host header, or cookies.

Events like SERVER_SELECTED or SERVER_CONNECTED occur after the load balancing decision has already been made, and HTTP_RESPONSE or SERVER_DATA occur after the server has already started communicating back, making them too late for initial pool selection.


Contribute your Thoughts:

0/2000 characters
Bernardo
4 hours ago
I think C, D, and E are key for load balancing.
upvoted 0 times
...
Audra
5 days ago
G is more about connection status, not selection.
upvoted 0 times
...
Christiane
11 days ago
I like C, E, and G. G could help with connections.
upvoted 0 times
...
Fidelia
16 days ago
F is not common in basic load balancing, though.
upvoted 0 times
...
Remedios
21 days ago
I feel like B and F could be relevant as well.
upvoted 0 times
...
Cordelia
26 days ago
A and C make sense, but I’m not sure about E.
upvoted 0 times
...
Yun
1 month ago
I’d go with A, C, and E. CLIENT_DATA is crucial too.
upvoted 0 times
...
Matthew
1 month ago
I agree, C is definitely important for HTTP requests.
upvoted 0 times
...
Miles
1 month ago
I think C, D, and E are key for load balancing.
upvoted 0 times
...
My
2 months ago
Surprised SERVER_DATA isn't on the list!
upvoted 0 times
...
Omer
2 months ago
I agree with C and E, but not sure about F.
upvoted 0 times
...
Lenora
2 months ago
Wait, SERVER_SELECTED isn't an event, is it?
upvoted 0 times
...
Milly
2 months ago
I think A, C, and E are the right picks!
upvoted 0 times
...
Marlon
2 months ago
Definitely going with C, E, and F.
upvoted 0 times
...
Noe
2 months ago
I practiced a question similar to this, and I think HTTP_RESPONSE was mentioned, but I'm not sure if it directly relates to pool selection.
upvoted 0 times
...
Odette
4 months ago
I feel like SERVER_SELECTED might be relevant too, but I can't recall if it's specifically for load balancing or something else.
upvoted 0 times
...
Margery
4 months ago
I'm not entirely sure, but I remember something about CLIENT_ACCEPTED being important for initial connections.
upvoted 0 times
...
Carmela
4 months ago
I think the HTTP_REQUEST event is definitely one of the key ones for selecting a pool. It seems to come up a lot in practice questions.
upvoted 0 times
...

Save Cancel