A customer's photo gallery site uses query parameters to filter photo search results. The site experiences high AEM Publish server load when users filter photos on the site. The customer would like…

Question

Options

• AignoreUrlParams configuration in dispatcher.any
• BDispatcher load balancing configuration
• CCache-Control Headers in dispatcher.any
• DVolume of assets being loaded at a time

• A
  5% (3)
• B
  7% (4)
• C
  67% (38)
• D
  21% (12)

Explanation

Cache-Control headers act as the gatekeeper for Dispatcher caching - if the Publish server is returning headers like no-cache or no-store on the filtered gallery responses, the Dispatcher will bypass its cache entirely for every request, sending them all directly to Publish and causing the observed load. This is the first thing to investigate because no other caching configuration matters if the response itself is marked uncacheable.

Option A (ignoreUrlParams) is relevant to query parameter handling but is a secondary concern - it controls how query strings affect cache key lookups, not whether the response can be cached at all; fixing it without addressing Cache-Control would still yield no caching. Option B (load balancing) distributes existing load across Publish instances but never reduces it - high load caused by a cache miss storm persists regardless of how well traffic is balanced. Option D (asset volume) could be a contributing factor to slow responses but is a symptom, not the architectural root cause of Publish being bypassed on every filter request.

Memory tip: Think "headers first, config second." Cache-Control headers are set by Publish and must permit caching before any Dispatcher .any configuration can help - check the lock before checking the key.

No community discussion yet for this question.