Cookie Persistenceis a Layer 7 persistence method that leverages an HTTP cookie to track a user session.
IP Independence:Unlike "Source Address Affinity" (which relies on the client's IP), Cookie persistence identifies the session base16d on a unique token provided by the BIG-IP system. This is crucial for environments where many users share a single gateway (NAT) or where a client's IP might change mid-session.
Encryption and Decryption:For the BIG-IP to insert or read a cookie, itmustbe able to see the HTTP header. If the traffic is encrypted end-to-end (SSL Pass-through), the BIG-IP cannot use cookie persistence. SSL must be terminated at the BIG-IP (Option B is false).
Security:By default, BIG-IP cookies are encoded, not clear text. Modern versions allow for easy encryption of these cookies to prevent information leakage (Option C is false).
Memory vs. Disk:The default behavior is "session-based" (In-memory). A cookie is only written to the client's file system (disk) if anExpirationis configured in the persistence profile (Option D is false).
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit