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 7 Question 43 Discussion

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

AEM SPA integration provides various design models. In an application the developer chooses to use AEM as a headless CMS without using the SPA Editor SDK framework.

What would be an advantage for this design model?

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:

Vonda
5 days ago
I think using AEM as a headless CMS without the SPA Editor SDK framework is a good idea.
upvoted 0 times
...

Save Cancel