Due to a change in application requirements, a BIG-IP Administrator needs to modify the configuration of a Virtual Server to include a Fallback…

A Fallback Persistence Profile is used when the primary persistence method fails (e.g., a client browser rejects a cookie). In this scenario, the BIG-IP system needs a reliable, alternative method to maintain session integrity. Source Address Affinity persistence, which uses the client's IP address, is the most common and recommended choice for a fallback profile. It is a "universal" method that does not depend on application-layer data and will almost always be available, ensuring connections from the same client are sent to the same pool member.

A. SSL: SSL persistence relies on the SSL Session ID. If the primary persistence failed, there is no guarantee the SSL session ID would be a reliable fallback.

B. Hash: Hash is a method used within various persistence profiles (including source address) to distribute traffic, not a standalone profile type suitable for fallback.

C. Universal: Universal persistence requires a custom iRule to define the persistence key. While powerful, it is more complex than necessary for a simple, reliable fallback mechanism.

- F5 Networks. (2021). BIG-IP Local Traffic Manager: Concepts. Chapter: "Understanding Persistence". Section: "Using fallback persistence". The documentation states, "A common profile to use as a fallback persistence profile is a source address affinity persistence profile... This is useful when the client is a browser that does not accept cookies, preventing cookie persistence from being used."

- F5 Networks. (2021). BIG-IP Local Traffic Manager: Implementations. Chapter: "Configuring Persistence". Section: "Implementing fallback persistence". This guide provides examples and reinforces that source address affinity is the typical choice for the fallback profile.