1Y0-351 · Question #202
Scenario: A NetScaler Engineer has configured COOKIEINSERT persistence with a timeout value of two minutes on an SSL LBvServer. The idle time requirement for the application itself CANNOT be…
The correct answer is D. COOKIEINSERT; zero. See the full explanation below for the reasoning.
Question
Scenario: A NetScaler Engineer has configured COOKIEINSERT persistence with a timeout value of two minutes on an SSL LBvServer. The idle time requirement for the application itself CANNOT be determined. Users report connections are intermittent. Once a session is disconnected, a user must re-authenticate in order to regain access. In order to correct this issue, the engineer should set persistence to __________ with a timeout of __________ minutes. (Choose the correct set of options to complete the sentence.)
Options
- ASOURCEIP; two
- BSSLSESSION; ten
- CSRCIPDESTIP; two
- DCOOKIEINSERT; zero
How the community answered
(21 responses)- A5% (1)
- B5% (1)
- C10% (2)
- D81% (17)
Community Discussion
8
Wesley A.Jun 11, 2026D is the move here. COOKIEINSERT with a timeout of zero means the persistence never expires on its own, which fixes the intermittent drops when the idle time of the app is unknown, because you are no longer racing against a two-minute clock that kills sessions before the app expects them to end.
Samuel O.Jun 27, 2026Saw this exact wording on my test, zeroed in on "cannot be determined" and picked D, timeout zero means never expire.
Nina C.Jun 27, 2026That tracks, though I keep tripping myself up because some vendor docs treat zero as "expire immediately" instead of "never expire," so now I flag any zero-value timeout question and ask myself which convention the specific technology uses before I commit to an answer.
Nina C.Jun 27, 2026D is right, setting the COOKIEINSERT timeout to zero means the persistence cookie has no expiration on the NetScaler side, so users stay pinned to the same server regardless of idle time. That directly fixes the re-authentication problem without needing to know the app's idle timeout, which is exactly the constraint given in the scenario.
Grace U.Jun 27, 2026D is the right call here, and the reasoning clicks once you see what a timeout of zero actually does on NetScaler, which is remove the expiration from the persistence cookie entirely so it lives until the browser session ends rather than cutting users off after an arbitrary two minutes. The COOKIEINSERT method itself was never the problem, only that fixed two-minute window forcing re-authentication on anyone who stepped away briefly.
Nina C.Jun 28, 2026Good catch on what zero actually means there, because I initially misread it as "expire immediately" rather than "no expiration set," and I bet that is exactly the trap they are counting on.
Kemal J.Jun 20, 2026SRCIPDESTIP with two minutes, SSL session ID is unreliable here.
Wesley A.Jun 21, 2026Kemal, good thinking on the timeout concern, but D is actually the right call here because SSL session IDs are tied directly to the client's negotiated session, which makes them more precise for persistence than source/destination IP pairs that can shift or be shared behind a NAT.