Which caching strategy is most effective for AEM as a Cloud Service?

Question

Options

• AServer-side rendering
• BClient-side caching with Content Fragments
• CDispatcher caching with CDN integration
• DSession-based caching for logged-in users

• A
  9% (3)
• B
  24% (8)
• C
  62% (21)
• D
  6% (2)

Explanation

Dispatcher caching with CDN integration is the most effective caching strategy for AEM as a Cloud Service because it offloads request handling to the edge layer, reducing load on publish instances and delivering content with minimal latency at scale - this is the architecture Adobe explicitly designed and recommends for AEMaaCS.

Why the distractors are wrong:

• A (Server-side rendering) is a rendering technique, not a caching strategy - SSR generates content but doesn't define how or where it's cached.
• B (Client-side caching with Content Fragments) mixes concerns; Content Fragments are a content model feature, and client-side caching alone provides no benefit to users who haven't yet visited the page.
• D (Session-based caching) is the opposite of effective in AEM - authenticated/session-tied responses are generally uncacheable, making this the least scalable approach.

Memory tip: Think "D for Dispatcher = Default caching hero." In AEMaaCS, the Dispatcher sits in front of the CDN layer, and together they form the two-tier caching shield that makes the platform cloud-ready. If an answer involves the Dispatcher + CDN on an AEM exam, it's almost always correct.

No community discussion yet for this question.