What would be the best persistence method for F5 to load balance traffic from clients via a single source IP (NAT) to multiple pool members with even distribution for HTTPS web applications? (Choose one answer)

A. Cookie persistence
B. Source address affinity persistence
C. SSL persistence
D. Destination address affinity persistence

Correct Answer: C

Brave-Dump Clients Votes

A 50%

C 50%

Comments

Anonymous User 2026-01-11 17:05:40

Selected Answers: A

Why this is correct:

Cookie persistence tracks users at the application layer, not by IP

Works correctly even when many clients share one NAT IP

Provides per-user session stickiness

Maintains even load distribution across pool members

❌ Why the other options are incorrect:

B. Source address affinity persistence – All users share one IP → all traffic goes to one server

C. SSL persistence – Based on SSL session ID; not reliable for even distribution and less commonly recommended

D. Destination address affinity persistence – Used for routing scenarios, not client persistence

Anonymous User 2026-02-24 11:33:57

Selected Answers: C

When traffic comes from a single source IP due to NAT, source address affinity persistence (B) won't work because all clients appear to come from the same IP, defeating even distribution. Cookie persistence (A) requires HTTP inspection and doesn't work well for HTTPS without SSL offloading. Destination address affinity (D) is unrelated to client tracking.
SSL persistence uses the SSL session ID to track individual clients, allowing F5 to distinguish between different clients even when they share the same source IP (NAT scenario), while still achieving even distribution across pool members for HTTPS traffic.