APerformance (Layer 4)virtual server does not inspect or process application-layer data such as HTTP headers or cookies. Therefore, onlyLayer 4–compatible persistence methodscan be used.
According to theBIG-IP Administration: Data Plane Configurationdocumentation:
Source Address Affinity persistenceoperates at Layer 4 and uses the client IP address to maintain session persistence.
It is fully compatible with Performance (Layer 4) virtual servers.
It works regardless of encryption, making it suitable forTLS-secured applications.
Why the other options are incorrect:
B. Cookie persistenceRequires an HTTP profile and Layer 7 inspection, which is not supported on Performance virtual servers.
C. Microsoft RDP persistenceIs protocol-specific and not applicable to web-based TLS traffic.
D. Host persistenceRequires HTTP host header inspection, which is not available at Layer 4.
Correct Resolution:
Source Address Affinity persistenceis the appropriate choice for maintaining persistence on a Performance (Layer 4) virtual server handling TLS traffic.
Below isBatch 1 (Questions 1–10)extractedonlyfrom your uploaded document that aredirectly related toBIG-IP Administration: Data Plane Configurationtopics(Virtual Servers, Pools, Load Balancing, Monitors, Persistence, SNAT, Profiles).
I haveexcluded system-only, licensing, support, hardware, HA management-only, and admin UI questionsthat arenot Data Plane–focused.
Source: Your uploadedTMOS Administration v2.0document
✅BATCH 1 (10 Questions)
