Where do compression policies need to be bound to take effect on traffic through a vServer?

Where do compression policies need to be bound to take effect on traffic through a vServer?

• A. Select the compression algorithm (gzip/deflate/identity).
• B. Disable the Citrix ADC compression feature at a global level.
• C. Enable compression on the associated bound services.
• D. Bind the default compression policies to the vServer.

Answer: (C)

Compression in Citrix ADC takes effect only where the traffic actually passes through a path that supports it. A vServer sits in front of one or more bound services, and the responses originate from those services before returning to the client. Even if a compression policy is defined and bound to the vServer, the policy will apply to traffic only if the bound services behind that vServer have compression enabled. This ensures the responses from those services can be compressed as they travel back through the vServer to the client. So, enabling compression on the associated bound services is the necessary step for the compression policy to take effect on traffic through the vServer.

Compression in Citrix ADC takes effect only where the traffic actually passes through a path that supports it. A vServer sits in front of one or more bound services, and the responses originate from those services before returning to the client. Even if a compression policy is defined and bound to the vServer, the policy will apply to traffic only if the bound services behind that vServer have compression enabled. This ensures the responses from those services can be compressed as they travel back through the vServer to the client.

So, enabling compression on the associated bound services is the necessary step for the compression policy to take effect on traffic through the vServer.