Adobe AD0-E134 Exam - Topic 3 Question 45 Discussion

Actual exam question for Adobe's AD0-E134 exam

Question #: 45
Topic #: 3

[All AD0-E134 Questions]

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

The customer asks for the following:

1. A centralized Header and Footer

2. The ability to create a variation for both the Header and Footer

3. Change the Header and Footer for specific time periods

4. The ability to restore a previous version for both the Header and Footer

What should the developer use to meet the requirements?

ACustom component

BContent fragment

CStatic template

DExperience fragment

Show Suggested Answer

Suggested Answer: C

For AEM as a Cloud Service, the correct format to use for OSGi configuration files is .cfg.json. This format is specifically designed for use in AEM as a Cloud Service and supports both structured and unstructured data, making it versatile for various configuration needs.

Steps to create and deploy OSGi configurations in .cfg.json format:

Create Configuration File: Create a .cfg.json file in your codebase, typically under the apps directory, for example:

/apps/myproject/config/org.apache.sling.commons.log.LogManager.cfg.json

Define Configuration: Add your configuration properties in JSON format:

{

'org.apache.sling.commons.log.level': 'debug',

'org.apache.sling.commons.log.file': 'logs/error.log'

}

Deploy to AEM: Deploy the configuration along with your code package to AEM as a Cloud Service. The configuration will be applied automatically.

AEM as a Cloud Service - OSGi Configuration

by Judy at Mar 23, 2025, 01:44 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Dorinda

5 months ago

Content fragments seem too limited for these requirements.

upvoted 0 times

...

Mauricio

5 months ago

Wait, can Experience fragments really handle time-based changes?

upvoted 0 times

...

Hyman

5 months ago

I vaguely recall something about versioning in Experience Fragments, which could help with the requirement to restore previous versions.

upvoted 0 times

...

Verona

6 months ago

This question seems similar to one we practiced about reusable components. I feel like a Custom Component could work, but I'm leaning towards Experience Fragments.

upvoted 0 times

...

Felicia

6 months ago

Totally agree, they allow for variations and versioning!

upvoted 0 times

...

Enola

6 months ago

I'm not entirely sure, but I think Content Fragments are more for structured content, not really for headers and footers.

upvoted 0 times

...

Tracey

6 months ago

I think Experience fragments are the way to go for this.

upvoted 0 times

...

Kenneth

6 months ago

Custom components might be more flexible for this.

upvoted 0 times

...

Brandon

7 months ago

I remember we discussed how Experience Fragments can be reused across different pages, which might fit the centralized Header and Footer requirement.

upvoted 0 times

...

Quentin

7 months ago

I'm leaning towards the Experience Fragment option. That seems to hit all the key requirements, including the ability to restore previous versions. I'll make sure to review the details carefully.

upvoted 0 times

...

Janine

7 months ago

Content fragments could work for the centralized header and footer, but I'm not sure they'd give us the flexibility we need for the other requirements. I'll have to think this through.

upvoted 0 times

...

Ettie

7 months ago

The ability to create variations and change the header/footer for specific time periods seems to point to using an Experience Fragment. I'll have to double-check the other requirements to be sure.

upvoted 0 times

...

Royce

7 months ago

This looks like a tricky one. I'll need to carefully consider the requirements and think through the best approach.

upvoted 0 times

...

Jarvis

8 months ago

I'm a little confused by the difference between a custom component and an Experience fragment. Can someone clarify how those two options would differ in this scenario?

upvoted 0 times

...

Gary

8 months ago

Okay, I think I've got a good handle on this. The Experience fragment is definitely the way to go - it'll give us the centralized control, variation options, and version history that the customer is looking for. I feel pretty confident about this one.

upvoted 0 times

...

Hoa

8 months ago

The content fragment option seems interesting, but I'm not sure if that would give us the level of control we need over the header and footer. I'm leaning more towards the Experience fragment solution.

upvoted 0 times

...

Melynda

8 months ago

Hmm, I'm a bit unsure about this one. The requirements mention being able to create variations and change the header/footer for specific time periods, so I'm not sure if a custom component or static template would be flexible enough.

upvoted 0 times

...

Peter

8 months ago

This looks like a pretty straightforward question. I think the Experience fragment option is the way to go here.

upvoted 0 times

...

Ozell

1 year ago

Experience fragment all the way, baby! Centralized, customizable, schedulable, and versionable? Sounds like the perfect solution to me. Time to experience the glory of the experience fragment!

upvoted 0 times

...

Arleen

1 year ago

Experience fragment is the way to go, no doubt. It's like the Swiss Army knife of AEM components - can do pretty much anything you need. Plus, who doesn't love a good experience fragment, am I right? *chuckles*

upvoted 0 times

Layla

12 months ago

D) Experience fragment

upvoted 0 times

...

Abel

1 year ago

C) Static template

upvoted 0 times

...

Stanton

1 year ago

B) Content fragment

upvoted 0 times

...

Louisa

1 year ago

A) Custom component

upvoted 0 times

...

Hector

1 year ago

Hmm, I'm not sure. Content fragment could work, but that might be overkill for just the header and footer. And a static template wouldn't give the flexibility they're looking for. Experience fragment sounds like the best fit to me.

upvoted 0 times

Stefany

1 year ago

D: Custom component could work too, but Experience fragment seems like the most efficient choice.

upvoted 0 times

...

Rodolfo

1 year ago

C: Experience fragment also allows you to restore previous versions, which is important for the customer's requirements.

upvoted 0 times

...

Roy

1 year ago

Yes, Experience fragment allows for variations, time-based changes, and version restoration.

upvoted 0 times

...

Lavonna

1 year ago

B: Yeah, I agree. It provides the flexibility to create variations and change content for specific time periods.

upvoted 0 times

...

Van

1 year ago

I agree, Experience fragment would provide the flexibility needed for centralized Header and Footer.

upvoted 0 times

...

Nidia

1 year ago

A: I think Experience fragment is the best option for this scenario.

upvoted 0 times

...

Felix

1 year ago

I think Experience fragment is the best option for this scenario.

upvoted 0 times

...

Leslie

1 year ago

Experience fragment definitely makes the most sense. Allows for easy reuse and updates across the site without having to update each individual page. Seems like the ideal solution for this use case.

upvoted 0 times

Wendell

1 year ago

Agreed, experience fragments are perfect for this scenario. They provide a centralized way to manage and update content across multiple pages.

upvoted 0 times

...

Valentin

1 year ago

D) Experience fragment

upvoted 0 times

...

Alverta

1 year ago

I think Experience fragment is the way to go here. It seems to check all the boxes - centralized management, variations, scheduling, and versioning. Sounds like a no-brainer to me.

upvoted 0 times