A multi-lingual citizen portal on CloudFront must vary cache by Accept-Language without disabling caching entirely. What should the developer configure?
Select an answer to reveal the explanation.
Short Explanation
Citizens speaking different languages need different cached pages—not a total cache blackout. Fold Accept-Language into the CloudFront cache key and keep caching on. You get the right language without throwing the CDN away.
Full Explanation
CloudFront cache policies can include selected headers such as Accept-Language in the cache key so localized responses are cached correctly. Disabling caching entirely, forwarding unbounded headers, or removing CloudFront sacrifices performance. Header-based cache variation is the intended pattern for multi-lingual portals.