Match each persistence method with the correct statement describing it:

Cookie persistence inserts or reads an HTTP Set-Cookie header to identify client sessions, which requires HTTP-layer inspection and does not function for non-HTTP protocols or when clients block cookies.

Source address persistence uses the client's source IP address as the session key, requiring only IP header inspection to maintain stickiness - it is the simplest persistence type, has no dependency on cookies or SSL state, and is often used when clients cannot accept cookies or when the application is non-HTTP.

SSL persistence extracts the SSL/TLS session ID from the handshake to maintain affinity, requiring the BIG-IP to inspect the TLS layer rather than simply reading the IP header.

Universal persistence relies on a user-written iRule to define a custom data element as the persistence key, requiring scripted logic and is not a built-in automatic mechanism.