A large digital agency has 10 TB of assets in their DAM where renditions for each Asset must be created without affecting performance for the authors. Which capability should the Architect recommend…

Question

Options

• AReduce the number of AEM Asset versions
• BCreate AEM multi-threaded workflow
• CUse AEM Asset Offloading
• DUpdate dispatcher configuration to cache Assetsa

• A
  21% (4)
• B
  63% (12)
• C
  5% (1)
• D
  11% (2)

Explanation

Multi-threaded workflows in AEM allow rendition processing to run in parallel across multiple threads, enabling the system to handle large-scale asset processing (like 10 TB of content) at high throughput without creating a backlog that degrades author responsiveness. By distributing the processing load concurrently, rendition jobs complete faster and avoid monopolizing the system resources authors depend on.

Why the distractors are wrong:

• A (Reduce versions): Version reduction frees up storage space but does nothing to improve how quickly or efficiently renditions are generated.
• C (Asset Offloading): Offloading distributes jobs to separate worker nodes - a valid concept - but in modern AEM contexts, multi-threaded workflows are the preferred, built-in mechanism for high-volume rendition generation without a complex topology.
• D (Dispatcher caching): The Dispatcher serves cached content to end-users; it plays no role in the rendition creation pipeline.

Memory tip: Think of the keyword "renditions at scale" - renditions are created via workflows, so any answer not involving workflows is suspect. When the requirement adds "without impacting authors," that points to making the workflow itself more efficient via multi-threading, rather than storage or caching solutions.

No community discussion yet for this question.