Exactly how Destination Address Affinity persistence will work ?

Did you see this:

Destination address affinity persistence You can optimize your server array with destination address affinity persistence. Destination address affinity persistence, also known as sticky persistence, directs requests for a certain destination IP address to the same server, regardless of which client made the request. This type of persistence provides the most benefits when load balancing caching servers. A caching server intercepts web requests and returns a cached web page if it is available. In order to improve the efficiency of the cache on these servers, it is necessary to send similar requests to the same server repeatedly. You can use the destination address affinity persistence type to cache a given web page on one server instead of on every server in an array. This saves the other servers from having to duplicate the web page in their cache, wasting memory.

https://support.f5.com/kb/en-us/products/lc_9_x/manuals/product/lc_config_guide_10_1/lc_persist_profiles.html

Destination Address persistence persists based on the destination address. Any request to the same destination IP will persist to the same member.

Great example is directly from the Session Persistence section of the support site.

Think of an example where LTM is used to balance HTTP sessions for clients across a pool of caching proxies. By directing requests for the same resource (destination) to the same proxy, the efficiency of the cache increases. Destination address affinity ensures that requests to, for example, www.f5.com* always go to the same proxy.

• - A bit of an oversimplification...but the basic premise remains valid.

This is applicable only to wilcard vserver which does not do any address or port translation. Is the understanding correct?

I have the same question. So what if a server turn off at this point? Will F5 route the request to a different server in the farm?