Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E134 Topic 6 Question 44 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 44
Topic #: 6
[All AD0-E134 Questions]

An AEM Developer needs to create a new component to help support a new product launch.

* The client is on AEM 6.5 on-premise with the latest version of WCM Core Components

* The component must include text, image, and a link

* The component must support multiple designs

Which process should the AEM Developer use to support the launch?

Show Suggested Answer Hide Answer
Suggested Answer: C

To implement a new component called 'Page Headline' which takes the text from the current page title instead of jcr:title, you should create a proxy component from the core title component and implement a Sling Model accordingly. Option C demonstrates the correct approach to achieve this functionality.

Here is a detailed explanation of Option C:

Create Proxy Component:

Create a new component in your project that will act as a proxy to the core title component. This involves creating a new component node in the repository that inherits from the core title component.

Example path: /apps/myproject/components/pageHeadline with sling:resourceSuperType set to core/wcm/components/title/v2/title.

Implement Sling Model:

Implement a Sling Model that adapts from SlingHttpServletRequest and Title.class, ensuring it overrides the text fetching logic to retrieve the title from the current page's title.

The model will use @ScriptVariable to inject the current page and @Self to access the core title component's logic.

@Model(adaptables = SlingHttpServletRequest.class, adapters = Title.class, resourceType = 'myproject/components/pageHeadline')

public class PageHeadline implements Title {

@ScriptVariable

private Page currentPage;

@Self @Via(type = ResourceSuperType.class)

private Title title;

@Override

public String getText() {

return currentPage.getTitle();

}

@Override

public String getType() {

return title.getType();

}

}

@Model Annotation: Specifies that this class is a Sling Model and adapts from SlingHttpServletRequest. It is also an adapter for Title.class and applies to the myproject/components/pageHeadline resource type.

@ScriptVariable: Injects the current Page object, which allows access to the current page's properties.

@Self @Via(type = ResourceSuperType.class): Injects the core title component, allowing the reuse of existing logic.

getText() Method: Overrides the getText() method to return the title from the current page instead of the jcr:title.

getType() Method: Delegates to the core title component's getType() method to maintain existing functionality.

This approach leverages the power of Sling Models and the core components to extend functionality while keeping the implementation clean and maintainable.


Adobe Experience Manager - Core Components

Sling Models Documentation

Contribute your Thoughts:

Shanda
3 days ago
I prefer option D because it involves creating a new Image with Text component that exposes the Core Components authoring dialogs.
upvoted 0 times
...
Christoper
5 days ago
Creating a new component by extending the Text Component seems like the most straightforward approach. We can add the image and link functionality without too much hassle. Plus, the Style System should give us the design flexibility we need.
upvoted 0 times
...
Nakita
6 days ago
Ah, this is a tricky one! Extending the Teaser Component from Core Components sounds like a good option, but I'm not sure if that will give us the flexibility we need for multiple designs. Maybe option D would be better to really customize the component for our needs?
upvoted 0 times
...
Eveline
11 days ago
I agree with you, Selma. Option A also allows for creating style variations to support multiple designs.
upvoted 0 times
...
Selma
16 days ago
I think option A is the best choice because it involves extending the Teaser Component from Core Components.
upvoted 0 times
...

Save Cancel