Which step can a Citrix Administrator take to use default compression policies?

Question

Options

• AEnable compression on the associated bound services.
• BSelect the compression algorithm (gzip/deflate/identity).
• CBind the default compression policies to the vServer.
• DDisable the Citrix ADC compression feature at a global level.

• B
  5% (1)
• C
  86% (18)
• D
  10% (2)

Explanation

Binding the default compression policies to the vServer (C) is correct because Citrix ADC ships with pre-built compression policies that are not active until explicitly bound to a virtual server - this is the required step to leverage them without creating custom policies from scratch.

Why the distractors are wrong:

• A - Enabling compression on bound services activates compression at the service level, but it does not invoke the default policies; policy binding controls which traffic gets compressed and how.
• B - Selecting the algorithm (gzip/deflate/identity) is a configuration detail within a compression action/policy, not the step that puts default policies into use.
• D - Disabling the global compression feature would prevent compression from working entirely - the opposite of the goal.

Memory tip: Think of default policies as pre-written rules sitting on a shelf. They only go to work when you bind them to a vServer - binding is always the "activation" step in Citrix ADC policy workflows (compression, rewrite, responder, etc.).

No community discussion yet for this question.