A client has an existing AEM site using components that proxy AEM WCM Core Components. The site uses simple page authoring without referenced content, The client wants to create a new experience on…

Question

Options

• AExperience Fragments
• BContent Fragments
• CAssets API
• DSling Model Exporter

• A
  4% (2)
• B
  71% (34)
• C
  17% (8)
• D
  8% (4)

Explanation

Content Fragments are the right choice because they are channel-agnostic, structured content assets stored in AEM that can be reused across multiple channels (web, mobile, email, kiosks, etc.) without requiring content refactoring - the existing page content can be modeled and consumed via the Content Fragment API in whatever new channel is being targeted.

Experience Fragments (A) are wrong here because they bundle content with layout/presentation (they're meant for reusable page sections, not raw content reuse across channels); they don't separate content from display, making them unsuitable for a different marketing channel with a different rendering context.

Assets API (C) is a DAM-focused API for managing binary assets like images and videos - it doesn't address structured content reuse across channels.

Sling Model Exporter (D) exports component model data as JSON from the existing AEM rendering pipeline - it's tied to the page/component structure and isn't designed to decouple content for independent multi-channel delivery.

Memory tip: Think of the word "Fragment" - Content Fragments = raw content (channel-neutral); Experience Fragments = content + experience/layout (channel-specific). When the requirement is "reuse content across channels," you want the one with no layout baggage: Content Fragments.

No community discussion yet for this question.