AD0-E117 practice question 13 of 15

A client is modernizing some of their AEM sites to go from static to editable templates so they can use the latest features around has the following…

A client is modernizing some of their AEM sites to go from static to editable templates so they can use the latest features around has the following parameters: • The client currently has a dozen static templates that they want to move to editable templates. • The existing pages use the parsys paragraph system for storing components. • Each page based on one of the static templates has its own custom properties tab that is unique for that template type. • The client wants template authors to be able to create the editable templates. Which approach should an Architect use to meet these requirements?

Answer options

A: 1. Use a new page component for editable templates based on the core components page component 2. Migrate page properties to respective components dialogues Correct answer

B: 1. Use a new page component for editable templates based on the core components page component 2. Convert page properties to policies

C: 1. Use the same page components for editable templates 2. Use a new template type for each static template

D: 1. Use the same page components for editable templates 2. Create a new editable template based on each of the existing page components

Correct Answer:

A. 1. Use a new page component for editable templates based on the core components page component 2. Migrate page properties to respective components dialogues

Explanation

The correct approach involves two key modernization steps. First, editable templates require a page component that is decoupled from the template structure, and the AEM WCM Core Page Component is the standard for this. A new proxy page component should be created that inherits from the Core Component. Second, the monolithic page properties dialogs from static templates should be refactored. Best practice is to move content-specific properties from the page level to the dialogs of the individual components they control. This creates a more modular, reusable, and maintainable component architecture, which is a primary benefit of moving to editable templates and Core Components.

Why Incorrect

B. Policies define design rules and constraints (e.g., allowed components), not page-specific content values. Converting content properties to policies is functionally incorrect.
C. Page components from static templates are tightly coupled to the template and are not compatible with the structure and policy model of editable templates.
D. This is incorrect for the same reason as C; static template page components cannot be reused. Editable templates are not based directly on page components in the same way.

References

1. Adobe Experience Manager as a Cloud Service Documentation. (2023). Editable Templates. Adobe. Retrieved from Adobe Experience League. This document explains the architecture of editable templates, highlighting the separation of the template from the page-rendering component.

2. Adobe Experience Manager Core WCM Components Documentation. (2023). Page Component. Section: "Usage". Adobe. Retrieved from GitHub. This guide shows that the Page Component is intended for use with editable templates and describes how it renders content based on the template's structure.

3. Adobe Experience Manager as a Cloud Service Documentation. (2023). Developing Templates. Section: "Policies". Adobe. Retrieved from Adobe Experience League. This reference clarifies the role of policies as design configurations, distinct from content entered in a component dialog.

Keep practicing

Take the free AD0-E117 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test