Q: 6
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?
Options
Discussion
Option D. but if the question had said the CDN stripped Via headers or servers ignored them, that'd change things.
D. The trap here is A, but Cloud CDN doesn't handle compression by itself so it's a web server config issue.
C/D? Not sure, but leaning D since most web servers stop compressing if a Via header is present.
Option D The Via header disables compression on a lot of default web server configs, seen that before.
Probably D, since web servers usually disable compression if requests have a Via header from proxies like Cloud HTTP(S) LB. Seen that in docs before. Not totally certain, open to other takes.
A isn’t it, D is more likely. Remember seeing a similar scenario in practice tests, where the Via header caused the web server to skip compression. But just to confirm, does the question specify if all load-balanced web servers are running identical configs? That could switch things between D and C.
C tbh. If the web servers behind the load balancer are set up with different compression types, that might cause inconsistent responses. I've seen similar practice questions recommend checking server config first. Exam guide suggests alignment across backends is important, but not totally sure here.
Its A
Don’t think it’s A, since Cloud CDN doesn’t handle compression itself. D is the issue here, web servers skip compression if they see a Via header from the load balancer. Seen similar reports in other exam threads.
Its D, web servers often skip compression if they see a Via header from the load balancer.
Be respectful. No spam.
