The administrator wants client request to be directed to the same pool member through the session based on the client IP address. Which persistence method should the administrator choose?

SSL persistence uses the SSL session ID as the persistence key, not the client IP address, making it unsuitable when IP-based stickiness is the requirement.

Destination address affinity persistence routes traffic based on the destination IP address (server side), not the client's source IP.

Cookie persistence relies on an HTTP cookie to track sessions and is not based on the client's IP address, requiring HTTP-level inspection.

Source address affinity persistence uses the client's source IP address as the session key so that all subsequent requests from the same IP are routed to the same pool member. This method operates at the network layer and is the correct choice when the requirement is IP-based session affinity regardless of the protocol or application content. It is commonly used for clients behind NAT or when cookie-based methods are unavailable.