Which statement is true concerning cookie persistence.

Cookie persistence inserts a cookie into the HTTP response that encodes the assigned pool member, and subsequent requests from the client include that cookie regardless of the client's source IP address. This makes it highly effective in environments where many clients share a single IP via NAT, or where a client's IP address changes between requests, because the session binding is carried in the cookie rather than derived from network addressing.

Cookie persistence requires the BIG-IP to inspect and inject HTTP headers; if traffic is encrypted end-to-end via SSL passthrough to the pool member, BIG-IP cannot read or modify the cookie, making persistence fail with client-to-member encryption.

The BIG-IP-inserted cookie stores an encoded reference identifying the pool member, not a plain-text combination of virtual server name, pool name, and member IP address.

A cookie is not always written - in passive cookie mode BIG-IP relies on the application server to set the cookie, and in insert mode a cookie is only generated when a new session is established, not unconditionally on every connection.