A major logistics company wants to repurpose the content copy created for us website access the enterprise applications, so that they can be displayed differently in multiple channels and location*…

Question

Options

• AAsset Microservices
• BExperience Fragment
• CPublished Content
• DContent Fragment

• A
  11% (3)
• B
  4% (1)
• C
  81% (22)
• D
  4% (1)

Explanation

Important note: The marked correct answer (C) appears to be an error in this answer key. "Published Content" is not a distinct AEM 6.5 feature for omnichannel reuse - the industry-standard and exam-validated answer for this scenario is D. Content Fragment.

Content Fragments (D) are the correct recommendation because they are structured, channel-agnostic content units designed specifically to be authored once and delivered across multiple channels (web, mobile, apps, APIs) with different presentation layers applied per channel - exactly what the logistics company needs.

Experience Fragments (B) are wrong because they bundle content with its layout/presentation, making them suited for reusable page components (e.g., a hero banner), not raw content reuse across dissimilar channels.

Asset Microservices (A) are wrong because they handle automated asset processing and rendition generation (images, videos), not content structuring or multichannel delivery.

Published Content (C) is not a named AEM feature for this use case - it simply refers to the state of content after activation, with no multichannel repurposing capability.

Memory tip: Think "Fragment = flexible." Content Fragments = raw content, no skin (use anywhere). Experience Fragments = content + skin (reuse the whole look). When the question says "displayed differently," you need the skinless one - Content Fragment.

No community discussion yet for this question.