QuestionQ13

Given a scenario, identify how to implement content fragments and experience fragments

An AEM application has a Header and Footer authored on each page.

The customer requests the following:

  1. A centralized Header and Footer
  2. The ability to create a variation for both the Header and Footer
  3. The ability to change the Header and Footer for specific time periods
  4. The ability to restore an earlier version of both the Header and Footer

What should the developer use to meet these requirements?

  • A Custom component
  • B Content fragment
  • C Static template
  • D Experience fragment
Explanation

Experience Fragments are reusable, fully laid-out groups of AEM components that can be referenced by multiple pages, making them appropriate for centralized headers and footers. They support variations, and their page-based implementation allows use of AEM page on/off timing and page-version restoration.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!