101 · Question #35
The incoming client IP address is 195.64.45.52 and the last five connections have been sent to members A, C, E, D and B. The incoming client IP address is 195.64.45.52 and the last five connections ha
The correct answer is C. 10.10.20.3:80C.10.10.20.3:80. With an active persistence record for client IP 195.64.45.52, BIG-IP directs the next connection to the previously assigned pool member rather than following the round-robin sequence.
Question
The incoming client IP address is 195.64.45.52 and the last five connections have been sent to members A, C, E, D and B. The incoming client IP address is 195.64.45.52 and the last five connections have been sent to members A, C, E, D and B. Given the virtual server, pool, and persistence definitions and statistics shown in the above graphic, which member will be used for the next connection.
Exhibit
Options
- A10.10.20.1:80
- B10.10.20.2:80B.10.10.20.2:80
- C10.10.20.3:80C.10.10.20.3:80
- D10.10.20.4:80D.10.10.20.4:80
- E10.10.20.5:80E.10.10.20.5:80
- FIt cannot be determined with the information given.
How the community answered
(26 responses)- A12% (3)
- C65% (17)
- E4% (1)
- F19% (5)
Why each option
With an active persistence record for client IP 195.64.45.52, BIG-IP directs the next connection to the previously assigned pool member rather than following the round-robin sequence.
10.10.20.1:80 is not the member mapped to client 195.64.45.52 in the persistence table shown in the graphic.
10.10.20.2:80 is not the persisted destination for this client IP according to the shown persistence statistics.
Because the client IP 195.64.45.52 already has a persistence record mapping it to pool member C (10.10.20.3:80) as shown in the graphic statistics, BIG-IP honors that persistence entry and sends the next connection to that same member. Persistence always takes priority over the load balancing algorithm, so 10.10.20.3:80 is selected regardless of which member would be next in the round-robin order.
10.10.20.4:80 is not mapped to client 195.64.45.52 in the current persistence record.
10.10.20.5:80 is not the persisted member for this client IP based on the shown statistics.
The persistence table and client IP together provide sufficient information to identify the correct member without ambiguity.
Concept tested: F5 BIG-IP source address persistence record lookup
Source: https://techdocs.f5.com/en-us/bigip-16-0-0/big-ip-local-traffic-management-basics/introduction-to-persistence.html
Topics
Community Discussion
No community discussion yet for this question.