A client plans to move a high-traffic e-commerce website to AEM as a Cloud Service. They want to optimize performance by implementing caching. Which combination of strategies should you recommend?

Question

Options

• ABrowser caching and synchronous replication
• BDispatcher caching with cache invalidation rules and CDN integration
• CManual cache updates and session-based caching
• DContent taxonomy optimization with browser-based caching

• A
  5% (1)
• B
  64% (14)
• C
  9% (2)
• D
  23% (5)

Explanation

Option B is correct because AEM as a Cloud Service is architected around the Dispatcher (Apache/CDN layer) as the primary caching tier - cache invalidation rules let you control which content is purged when authors publish changes, while CDN integration (Fastly, by default) handles global edge caching to reduce origin load for high-traffic sites like e-commerce.

• A is wrong because synchronous replication is a performance anti-pattern; it blocks publishing workflows and has nothing to do with caching strategy.
• C is wrong because manual cache updates don't scale for high-traffic sites, and session-based caching actively undermines CDN effectiveness (personalized/session content can't be cached at the edge).
• D is wrong because content taxonomy is an information architecture concern, not a performance caching strategy - it doesn't interact with Dispatcher or CDN layers.

Memory tip: Think "D-C" - Dispatcher + CDN is the AEM caching stack. Anything that mentions "manual," "session," or "synchronous" in a high-traffic context is a red flag, since AEM Cloud is built for automated, stateless, distributed delivery.

No community discussion yet for this question.