What is the most likely cause of the problem?

You have configured Cloud CDN using HTTP(S) load balancing as the origin for cacheable content. Compression is configured on the web servers, but responses served by Cloud CDN are not compressed.

What is the most likely cause of the problem?
A . You have not configured compression in Cloud CDN.
B . You have configured the web servers and Cloud CDN with different compression types.
C . The web servers behind the load balancer are configured with different compression types.
D . You have to configure the web servers to compress responses even if the request has a Via header.

View Answer

Answer: D

Explanation:

If responses served by Cloud CDN are not compressed but should be, check that the web server software running on your instances is configured to compress responses. By default, some web server software will automatically disable compression for requests that include a Via header. The presence of a Via header indicates the request was forwarded by a proxy. HTTP proxies such as HTTP(S) load balancing add a Via header to each request as required by the HTTP specification. To enable compression, you may have to override your web server’s default configuration to tell it to compress responses even if the request had a Via header.