New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E134 Exam - Topic 4 Question 51 Discussion

Actual exam question for Adobe's AD0-E134 exam
Question #: 51
Topic #: 4
[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: A

Extend the Teaser Component from Core Components

Create style variations to be used in the Style System** Comprehensive Explanation of Correct Answer Only: The Teaser Component from Core Components is a component that allows authors to display a title, description, image and link for a teaser item. The component supports multiple designs and can be extended to add custom features or logic. The Style System allows authors to define style variations for components without requiring code changes or new templates. Reference: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/teaser.html?lang=en https://experienceleague.adobe.com/docs/experience-manager-core-components/using/components/style-system.html?lang=en


by Javier at Aug 04, 2025, 05:05 AM

Limited Time Offer

25%

Off

Get Premium AD0-E134 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Beatriz
2 months ago
Wait, can you really manipulate images in the Text Component? Sounds odd.
upvoted 0 times
...
Twanna
2 months ago
Totally agree, extending the Teaser Component makes sense!
upvoted 0 times
...
Alva
3 months ago
Option B could work too, but I prefer A for flexibility.
upvoted 0 times
...
Oren
3 months ago
Not sure about option D, seems like overkill for a simple component.
upvoted 0 times
...
Annmarie
3 months ago
I think option A is the best choice for extending existing components.
upvoted 0 times
...
Shenika
3 months ago
Option D seems to align with what we practiced about combining components, but I’m not clear on how to expose the authoring dialogs correctly.
upvoted 0 times
...
Caitlin
4 months ago
I feel like extending the Text Component could work, but I’m uncertain about enabling image manipulations through policy.
upvoted 0 times
...
Daniel
4 months ago
I think option B sounds familiar because it involves creating a new component, but I can't recall if modifying HTL for images is necessary.
upvoted 0 times
...
Charolette
4 months ago
I remember we discussed extending the Teaser Component in class, but I'm not sure if that's the best approach for this requirement.
upvoted 0 times
...
Luke
4 months ago
I'm feeling pretty confident about this one. I think option C is the way to go - extending the Text Component from Core Components and enabling image manipulations via policy. That way, I can reuse the existing functionality and just add the image support.
upvoted 0 times
...
Crista
4 months ago
Okay, let me think this through. The key requirements are text, image, and a link, with support for multiple designs. I think option D might be the best approach - creating a new Image with Text component that leverages the Core Components authoring dialogs and using a policy to define the design variations.
upvoted 0 times
...
Irma
5 months ago
Hmm, I'm a bit unsure about this one. I'm not sure if extending the Teaser Component is the best approach since the requirement is for a new component, not just style variations. Maybe I should consider option B or D instead.
upvoted 0 times
...
Serina
5 months ago
This looks like a straightforward question. I think I'll go with option A - extending the Teaser Component from Core Components and using the Style System to create different design variations.
upvoted 0 times
...
Lauran
5 months ago
I believe creating a new Image with Text component that exposes the Core Components authoring dialogs would be the best option.
upvoted 0 times
...
Barrett
5 months ago
Haha, Option C is like trying to put a square peg in a round hole. Enabling image manipulations on the Text Component? That's like putting lipstick on a pig!
upvoted 0 times
Katie
5 months ago
I agree! Definitely not the best choice.
upvoted 0 times
...
Kanisha
5 months ago
Just use option A and keep it simple!
upvoted 0 times
...
Sylvia
5 months ago
Option C? Really? That's a stretch.
upvoted 0 times
...
Deja
5 months ago
Totally! It doesn't fit the requirements.
upvoted 0 times
...
...
Benton
6 months ago
But wouldn't it be better to create a new component by extending the Text Component from Core Components?
upvoted 0 times
...
Johnna
7 months ago
I agree, that way they can create style variations to be used in the Style System.
upvoted 0 times
...
Richelle
7 months ago
I'd go with Option B. Extending the Text Component and adding image support is a more straightforward solution than creating a whole new component.
upvoted 0 times
...
France
7 months ago
I think the AEM Developer should extend the Teaser Component from Core Components.
upvoted 0 times
...
Hassie
7 months ago
Option D seems like the best approach. Creating a custom component with the core component dialogs is a clean way to extend functionality while keeping things modular.
upvoted 0 times
Shawna
5 months ago
I think option D is the way to go. It allows for customization while still using the core component dialogs.
upvoted 0 times
...
...

Save Cancel