The issue arises because Cloud CDN is not respecting the caching headers defined by the application team. The correct approach is to configure the USE_ORIGIN_HEADERS caching mode, which instructs Cloud CDN to cache content based on the Cache-Control headers provided by the backend. The application team has already defined caching behavior in their responses, so using this mode ensures Cloud CDN honors those directives. Other modes like CACHE_ALL_STATIC or FORCE_CACHE_ALL override origin headers, which would ignore the application's specific caching rules and could lead to improper caching behavior.