Which persistence mechanism does NOT consume memory on the Service Engine?

Question

Options

• AHTTP Cookie Persistence
• BClient IP Persistence
• CApp Cookie Persistence
• DTLS Persistence

• A
  5% (1)
• B
  91% (20)
• C
  5% (1)

Explanation

Client IP Persistence is stateless - the Service Engine can deterministically route traffic using a hash of the client's IP address, requiring no stored mapping table and therefore consuming no memory on the Service Engine.

Why the distractors are wrong:

• A (HTTP Cookie): The Service Engine must maintain an in-memory table mapping cookie values to backend servers.
• C (App Cookie): Similar to HTTP Cookie, the Service Engine must store a lookup table to correlate application-set cookies with specific servers.
• D (TLS Persistence): The Service Engine must keep an in-memory TLS session ID-to-server mapping table for the duration of the session.

Memory tip: Think of it this way - anything the Service Engine has to remember (cookies, TLS session IDs) costs memory. A client's IP address is just math - the Service Engine hashes it on the fly and never needs to store anything.

No community discussion yet for this question.