1Y0-351 · Question #226
Which NetScaler caching type requires proxy configuration on all client devices?
The correct answer is C. FORWARD. See the full explanation below for the reasoning.
Question
Which NetScaler caching type requires proxy configuration on all client devices?
Options
- ASOCKS
- BREVERSE
- CFORWARD
- DTRANSPARENT
How the community answered
(43 responses)- A2% (1)
- B5% (2)
- C81% (35)
- D12% (5)
Community Discussion
6
Mei-Ling H.Jun 26, 2026C is correct. Forward proxy caching requires each client device to be configured with the proxy address, because the client deliberately sends its requests through the proxy rather than directly to the destination, so without that manual configuration on the client side the traffic never passes through the NetScaler cache at all.
Nina C.Jun 29, 2026Right, and I think that is exactly why the exam contrasts forward proxy with a transparent proxy setup, where the network itself intercepts and redirects traffic to the cache so no client configuration is needed at all.
Nina C.Jun 24, 2026Got this exact one on my exam last month, froze for a second, then remembered forward proxy means the clients have to know about it, so C.
Ingrid P.Jun 26, 2026Forward proxy caching is the one that demands explicit proxy settings on every client, because the client must be told to send its HTTP requests to the NetScaler instead of the origin server directly. That client-side configuration step is exactly what distinguishes it from transparent caching, which intercepts traffic without the client knowing anything about a proxy.
Nina C.Jun 28, 2026Right, and that explicit client config is also what makes forward proxies handy for per-user authentication and access control, since every request arrives already identified by the client that sent it, which transparent caching just cannot do.
Giselle K.Jun 26, 2026FORWARD proxy is the right call here, though the question could be more precise since it is really about explicit proxy mode requiring each client to have the proxy address configured in its browser or OS settings. TRANSPARENT is the tempting trap because it sounds like it hides complexity from clients, and it does at the network level, but that works via policy-based routing or WCCP at the infrastructure layer, not per-device config.