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 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?

Show Suggested Answer Hide 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

Contribute your Thoughts:

Hector
3 days 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
...
Leslie
14 days 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
...
Alverta
16 days 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
...
Bok
18 days ago
But wouldn't a Custom component also work for this scenario?
upvoted 0 times
...
Jettie
23 days ago
I agree, Experience fragment allows for variations and versioning.
upvoted 0 times
...
Minna
26 days ago
I think the developer should use Experience fragment for this.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77