Which statement is true for Avi to compress an HTTP response?

Question

Options

• ACaching must be disabled.
• BThe Web Application Firewall must be disabled.
• CClient round trip time must be greater than 100ms.
• DClient's Accept-Encoding header must be in the request.

• C
  6% (1)
• D
  94% (15)

Explanation

Option D is correct because HTTP compression requires the client to explicitly signal its ability to handle compressed content via the Accept-Encoding request header (e.g., Accept-Encoding: gzip, deflate). Without this header, Avi has no way to know whether the client can decompress the response, so it will not compress it.

Why the distractors are wrong:

• A - Caching and compression are independent features; both can be active simultaneously without conflict.
• B - The Web Application Firewall operates on a different layer and has no bearing on whether HTTP compression is applied.
• C - There is no round-trip time threshold requirement for compression; it is purely driven by client capability negotiation, not network latency.

Memory tip: Think of Accept-Encoding as the client asking permission to receive compressed data - if the client never asks, the server never compresses. The phrase "Accept before you compress" can help you remember that the client's header must come first.

No community discussion yet for this question.