AWS Certified CloudOps Engineer Associate SOA-C03 Practice Question

CloudFront creates a separate cache entry for every unique cache key. If the distribution's cache policy is currently configured to forward query strings, those parameters are included in the cache key, so every utm-style variant of hero.png triggers its own origin fetch on first request-even though the object never varies. Attaching a cache policy that omits query strings from both the cache key and the origin request causes all URL variants to map to the same cached object, maximizing the hit ratio and sharply reducing origin traffic. Origin Shield can lessen miss traffic but still keeps distinct objects for each query string. Field-level encryption and signed URLs address security, not caching. A Lambda@Edge function could strip parameters, but that adds extra cost and complexity compared with simply changing the cache policy.