A BIG-IP Administrator needs to apply persistence to a virtual server that is configured as a Performance (Layer 4) virtual server that allows access…

A Performance (Layer 4) virtual server operates at the transport layer (TCP/UDP) and does not have visibility into application-layer data. Therefore, persistence methods requiring application data inspection, such as cookies or host headers, cannot be used. Source Address Affinity persistence works by tracking the client's source IP address, which is available at Layer 3. This makes it a compatible and effective persistence method for a Performance (L4) virtual server, as it does not require any application-layer processing.

B. Cookie persistence requires an HTTP profile to inspect and insert HTTP cookies, which is not available on a Performance (L4) virtual server.

C. Microsoft RDP persistence is specific to the RDP protocol and requires application-layer inspection, which is incompatible with a Performance (L4) virtual server.

D. Host persistence uses the HTTP Host header for persistence decisions, requiring an HTTP profile not present on a Performance (L4) virtual server.

1. F5 Networks. (2021). BIG-IP Local Traffic Manager: Concepts, Chapter 3: Virtual Servers. F5 Cloud Docs. Retrieved from https://techdocs.f5.com/kb/en-us/products/big-ipltm/manuals/product/ltm-concepts-13-1-0/3.html. (See section: "Virtual server types", specifically "Performance (Layer 4) virtual server").

2. F5 Networks. (2021). K7786: Overview of BIG-IP LTM persistence profiles. F5 Support. Retrieved from https://support.f5.com/csp/article/K7786. (See section: "Source address affinity persistence").