Question

A SysOps administrator manages a CloudFront distribution in front of an Application Load Balancer serving a product catalog application. The application returns different content based on a 'category' query string parameter, but users report they consistently see the same product list regardless of the category they select. CloudWatch shows a high cache hit ratio at CloudFront. What is the MOST likely cause and the correct remediation?

Accepted Answer

The cache behavior's cache policy is not configured to include the 'category' query string in the cache key; update the cache policy to forward and cache based on the required query strings.

Answer

The origin's health check is failing; configure an origin failover group so CloudFront routes to a healthy secondary origin.

Answer

The distribution's default TTL is set to 0; increase the minimum and default TTL so CloudFront caches distinct responses per category.

Answer

The ALB is not sticky; enable session stickiness on the target group so each category request reaches the correct backend instance.