AD0-E117 · Question #19
A client's marketing pages are generally slow to load which is causing a significant drop in sales. All other AEM pages load within expected performance guidelines regardless of whether the visitor…
The correct answer is D. Convert the marketing pages to a responsive design instead of an adaptive design. Converting to responsive design solves the root cause: the marketing pages use adaptive design, which requires server-side device detection to serve separate desktop/mobile experiences, making it nearly impossible for the AEM Dispatcher to cache those pages effectively…
Question
A client's marketing pages are generally slow to load which is causing a significant drop in sales. All other AEM pages load within expected performance guidelines regardless of whether the visitor is being served the desktop or mobile experiences. The marketing pages typically get slower when multiple external campaigns such as Facebook and AdWords drive traffic to those pages. The page performance tends to dip during high traffic periods. Internal campaign clicks such as those from hero images use similar campaign codes as external campaign traffic. What should the Architect do to resolve this issue?
Options
- AModify the dispatcher.any file's section to ignore campaign-based URL parameters
- BSet AEM to use GZIP compression instead of the web server's compression
- CAdd a new dispatcher farm to assist with the client's marketing pages
- DConvert the marketing pages to a responsive design instead of an adaptive design
How the community answered
(45 responses)- A7% (3)
- B16% (7)
- C2% (1)
- D76% (34)
Explanation
Converting to responsive design solves the root cause: the marketing pages use adaptive design, which requires server-side device detection to serve separate desktop/mobile experiences, making it nearly impossible for the AEM Dispatcher to cache those pages effectively - especially when campaign URL parameters (shared by both external and internal traffic) create additional cache variations that force every request back to AEM, causing performance collapse under high load.
Option A is tempting but incomplete - ignoring campaign parameters in dispatcher.any helps with URL-based cache busting but doesn't fix the adaptive design's device-detection problem, which prevents the Dispatcher from serving a single cached response to all visitors.
Option B is irrelevant - GZIP compression reduces payload transfer size but does nothing for the server-side rendering bottleneck caused by repeated cache misses hitting AEM directly during traffic spikes.
Option C treats the symptom, not the disease - adding a Dispatcher farm increases capacity for uncached requests but still leaves every marketing page request hitting AEM because adaptive design prevents proper caching; you'd just have more farms doing unnecessary work.
Memory tip: Think "Adaptive = AEM decides per device = can't cache = slow under load; Responsive = one HTML, CSS decides layout = Dispatcher caches once, serves everyone = fast." If the page must know your device before rendering, it can't be cached efficiently.
Topics
Community Discussion
No community discussion yet for this question.