Refer to the exhibit. An organization is reporting slow performance accessing their Intranet website, hosted in a public cloud. All employees use a single Proxy Server with the public IP of 104.219.11

Changing the source address to a specific IP address (104.219.110.168/32) is not a configuration setting to fix this issue; it describes the problem, not a solution for BIG-IP.

While load balancing methods like Least Connection can help distribute new connections, they do not address the issue of session persistence when all connections appear to originate from a single source IP address.

Fallback persistence is used if the primary persistence method fails; changing it to source_addr would exacerbate the problem since source_addr is the root cause of the issue when using a proxy.

Since all users connect via a single proxy server (104.219.110.168), the BIG-IP will see all connections as coming from this single source IP address, making source IP persistence ineffective and potentially overloading a single backend server. Changing the default persistence profile to cookie ensures that each individual user, identified by a unique cookie, is consistently directed to the same backend server, maintaining session state and distributing the load more evenly among servers, resolving the performance issue.