Scenario: A Citrix Administrator executed the command below: > set httpscallout httpcallout -cacheForSecs 129 This command changes the cache duration of the HTTP _______ to be set to 120 seconds…

Question

Options

• Acallout request
• Brequest
• Cresponse
• Dcallout response

• A
  4% (1)
• B
  4% (1)
• D
  92% (23)

Explanation

Option D is correct because the -cacheForSecs parameter in a Citrix NetScaler HTTP callout configuration controls how long the callout response - the answer returned by the external HTTP callout server - is stored in cache. Caching the response avoids repeated outbound callout requests for the same lookup within the specified window.

Why the distractors fail:

• A (callout request) - Requests are sent outbound; they are never cached. You cache what comes back, not what goes out.
• B (request) - Same logic as A, and it also omits the word "callout," making it doubly incorrect in this context.
• C (response) - Partially right (it is a response), but the generic term "response" would refer to the main client response, not the external server's reply. The precise term is callout response.

Memory tip: Think of it as caching the answer to your question - the callout fires a question (request) at an external server, and it's the callout response (the answer) that gets cached for reuse. Cache = store the reply, not the query.

No community discussion yet for this question.