101 · Question #544
A website is using source address persistence with a 30 second timeout. A client is idle for 35 seconds. What happens to their connection?
The correct answer is D. The Client request is load balanced. When a source address persistence timeout expires, the load balancer no longer has a binding for that client IP, so the next request is treated as new and distributed normally.
Question
A website is using source address persistence with a 30 second timeout. A client is idle for 35 seconds. What happens to their connection?
Options
- AThe client receives a "404 Page Not Found'" error
- BThe client connection is dropped
- CThe client remains on the same server
- DThe Client request is load balanced
How the community answered
(19 responses)- A11% (2)
- B5% (1)
- C5% (1)
- D79% (15)
Why each option
When a source address persistence timeout expires, the load balancer no longer has a binding for that client IP, so the next request is treated as new and distributed normally.
A 404 error is an HTTP application-level response indicating a missing resource, unrelated to load balancer persistence timeouts.
The client connection itself is not dropped - the persistence record expires silently, and subsequent requests simply go through load balancing.
The client will NOT remain on the same server because the persistence entry has expired, removing the server affinity.
Source address persistence (source IP affinity) maintains a mapping between a client IP and a specific server for the duration of the timeout. After 35 seconds - exceeding the 30-second timeout - the persistence entry is purged from the table, and the client's next request is routed by the standard load balancing algorithm as if it were a new connection.
Concept tested: Load balancer source IP persistence timeout behavior
Source: https://www.f5.com/services/resources/glossary/persistence
Topics
Community Discussion
No community discussion yet for this question.