Format
Focused questions and practical troubleshooting
Practice explaining Dispatcher caching, invalidation, and stale-content diagnosis in AEM.
AI Summary
Practice explaining Dispatcher caching, invalidation, and stale-content diagnosis in AEM.
Quick Facts
This snapshot gives the page context in a fast, scannable format.
Format
Focused questions and practical troubleshooting
Interview practice
Use these explanations to practice the mechanism and a safe diagnostic sequence.
Dispatcher is an AEM caching and load-balancing tool used with a web server. It can serve eligible cached responses and forward requests to publish instances. Its filters, cache rules and environment configuration determine actual behavior.
Deletion removes a cached file. With auto-invalidation, Dispatcher can mark content as potentially stale and compare its timestamp with a statfile when it is next requested. Exact behavior depends on the configured rules.
Compare the same host and path directly on the relevant publish instance and through Dispatcher. If publish is stale, check publication and the content version. If publish is current, investigate Dispatcher rules, invalidation and any CDN or browser cache before choosing a targeted remedy.
Repeat the same request against each relevant delivery path and compare the content, headers and timestamps. Check publish and Dispatcher logs for the invalidation event and make a further content change in a safe environment to test recurrence.
Continue learning
Connect the focused answers with the broader practice track.
Sources
Use these references to keep the guide grounded in official product documentation and the most relevant SplashRide pages.