AD0-E117 · Question #12
A client using AEM 6.5 on-premise is experiencing an unsustainable repository growth of 100Gb a day. After investigation, an Architect finds out that the DAM is causing this issue. Each image…
The correct answer is B. Split WCM and DAM in separate instances, set up Connected Assets, and re-implement article-. Splitting WCM and DAM into separate AEM instances with Connected Assets directly solves both problems: it offloads the massive rendition storage burden to a dedicated DAM instance (preventing the 100GB/day growth from crushing the WCM repository), and re-implementing the…
Question
A client using AEM 6.5 on-premise is experiencing an unsustainable repository growth of 100Gb a day. After investigation, an Architect finds out that the DAM is causing this issue. Each image uploaded to the DAM triggers the creation of approximately 100 renditions, necessary by business to consume in different channels and systems. The client also complains about stale content reported by site visitors happening randomly in pages where article-related components are present. How should the Architect address these issues?
Options
- ALeverage AEM Adaptive Image Servlet, cache image variations in Dispatcher, and reimplement
- BSplit WCM and DAM in separate instances, set up Connected Assets, and re-implement article-
- CLeverage AEM Adaptive Image Servlet cache image variations in Dispatcher, and implement a
- DSplit WCM and DAM in separate instances, set up Connected Assets, and implement a workflow
How the community answered
(37 responses)- A8% (3)
- B43% (16)
- C32% (12)
- D16% (6)
Explanation
Splitting WCM and DAM into separate AEM instances with Connected Assets directly solves both problems: it offloads the massive rendition storage burden to a dedicated DAM instance (preventing the 100GB/day growth from crushing the WCM repository), and re-implementing the article components - rather than just adding a workflow - is what properly fixes the stale content issue by correcting the underlying cache invalidation logic tied to those components.
Why A and C are wrong: Both rely on AEM Adaptive Image Servlet + Dispatcher caching, which generates renditions on-demand rather than storing them - useful for web delivery, but it doesn't serve the 100 renditions required for multiple external channels and systems. These approaches optimize delivery without solving the storage or multi-channel asset consumption requirement.
Why D is wrong: It correctly splits WCM/DAM and uses Connected Assets, but "implement a workflow" is the wrong fix for stale content on article components. Workflows govern asset processing, not component-level cache invalidation; the stale content problem requires re-implementing the components themselves with proper replication/invalidation behavior.
Memory tip: Think "SCALE then FIX" - when DAM is causing repository bloat at scale, separate it (WCM/DAM split + Connected Assets); when page components serve stale data, re-implement them (not patch with a workflow). Option B is the only answer that does both correctly.
Topics
Community Discussion
No community discussion yet for this question.