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

Question

Options

• ABind the default compression policies to the virtual server.
• BEnable compression on the associated bound services.
• CDisable the Citrix ADC Compression feature at a global level.
• DSelect the compression algorithm (gzip/deflate/identity).

• A
  87% (33)
• B
  5% (2)
• C
  3% (1)
• D
  5% (2)

Explanation

Binding the default compression policies to the virtual server (A) is the correct step because Citrix ADC ships with built-in compression policies that are inactive until explicitly bound to a virtual server - binding is the mechanism that activates them without requiring custom policy creation.

Why the distractors are wrong:

• B - Enabling compression on bound services enables the feature at the service level, but does not activate the default policies; policies must be bound separately to the virtual server.
• C - Disabling the compression feature globally would prevent compression from working entirely - the opposite of the goal.
• D - Selecting a compression algorithm (gzip/deflate/identity) is a configuration detail within a policy, not the administrative step required to use default policies.

Memory tip: Think of it as a plug-and-socket relationship - the default policies exist as ready-made "plugs," but they only do work once you "socket" them into a virtual server via binding. If you don't bind, the feature sits idle no matter what else you configure.

No community discussion yet for this question.