Adobe Exam AD0-E134 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

Ozell

1 months 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

2 months 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

15 days ago

D) Experience fragment

upvoted 0 times

...

Abel

24 days ago

C) Static template

upvoted 0 times

...

Stanton

27 days ago

B) Content fragment

upvoted 0 times

...

Louisa

28 days ago

A) Custom component

upvoted 0 times

...

Hector

2 months 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

27 days ago

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

upvoted 0 times

...

Rodolfo

28 days ago

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

upvoted 0 times

...

Roy

1 months ago

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

upvoted 0 times

...

Lavonna

1 months ago

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

upvoted 0 times

...

Van

1 months ago

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

upvoted 0 times

...

Nidia

2 months ago

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

upvoted 0 times

...

Felix

2 months ago

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

upvoted 0 times

...

Leslie

3 months 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

2 months 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

2 months ago

D) Experience fragment

upvoted 0 times

...

Alverta

3 months 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