A SysOps admin observes that an Amazon CloudFront distribution is seeing a cache hit rate below 10%. Which configuration changes will help raise the cache hit rate for this distribution? (Select two.)

A low cache hit rate means CloudFront is frequently fetching content from the origin instead of serving it from its edge locations. To improve this, you want to maximize the reusability of cached objects. Forwarding only necessary cookies, query strings, and headers (instead of all or none) ensures that CloudFront caches objects based on fewer variations. If different requests vary only by unnecessary parameters, CloudFront will treat them as distinct objects, reducing the cache hit rate. By forwarding only essential parameters, more requests can hit the same cached object. Increasing the object Time-To-Live (TTL) values tells CloudFront to keep objects in the cache for a longer duration before checking with the origin for updates. Longer TTLs mean objects are served from the cache more frequently, directly increasing the cache hit rate. Setting the Viewer Protocol Policy to require HTTPS only, restricting access with presigned URLs/cookies, and turning on automatic compression are security, access control, or performance optimization features, but they do not directly impact the cache hit rate.