Cyber Monday 2024! 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 6 Question 34 Discussion

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

With AEM as a Cloud Service, which format should be used for the OSGI configuration files?

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:

Frederica
2 months ago
Wait, is this a trick question? I bet the answer is 'all of the above' and you have to know the proper use case for each format.
upvoted 0 times
Monroe
21 days ago
C) .cfg.json
upvoted 0 times
...
Elke
23 days ago
B) xml
upvoted 0 times
...
Lizette
24 days ago
A) config
upvoted 0 times
...
...
Letha
2 months ago
Hold up, is there a 'config' option? That's just too easy, it's gotta be the .cfg.json format.
upvoted 0 times
Carey
1 months ago
Yeah, I'm leaning towards .cfg.json as well. It just makes more sense.
upvoted 0 times
...
Aleisha
1 months ago
I agree, .cfg.json seems like the right choice for OSGI configuration files.
upvoted 0 times
...
Penney
1 months ago
I think the 'config' option is too easy, I would go with .cfg.json.
upvoted 0 times
...
...
Lizette
2 months ago
That's a valid point, but I still think C) .cfg.json is the best choice for AEM as a Cloud Service.
upvoted 0 times
...
Malinda
2 months ago
Definitely .cfg.json, it's the only option that makes sense for a cloud-native AEM deployment.
upvoted 0 times
William
1 months ago
Definitely .cfg.json, it's the only option that makes sense for a cloud-native AEM deployment.
upvoted 0 times
...
Rosann
1 months ago
D) .cfg
upvoted 0 times
...
Shaquana
2 months ago
C) .cfg.json
upvoted 0 times
...
Emily
2 months ago
B) xml
upvoted 0 times
...
Leonida
2 months ago
A) config
upvoted 0 times
...
...
Kerrie
2 months ago
I disagree, I believe the answer is D) .cfg because it's a common format used for OSGI configuration files in AEM.
upvoted 0 times
...
Lizette
3 months ago
I think the answer is C) .cfg.json because it's the recommended format for OSGI configuration files in AEM as a Cloud Service.
upvoted 0 times
...
Freeman
3 months ago
Hmm, I thought it was still xml. AEM as a Cloud Service is new to me, so I'm not 100% sure.
upvoted 0 times
Viva
2 months ago
I'm not sure, but I think it's .cfg.json
upvoted 0 times
...
Lorean
2 months ago
I'm pretty sure it's config
upvoted 0 times
...
Miss
2 months ago
No, I believe it's .cfg
upvoted 0 times
...
Ollie
2 months ago
I think it's .cfg.json
upvoted 0 times
...
...
Jani
3 months ago
I'm pretty sure it's .cfg.json, that's the new standard for AEM as a Cloud Service.
upvoted 0 times
Gene
2 months ago
Yeah, I agree. It's the new standard for OSGI configuration files in AEM as a Cloud Service.
upvoted 0 times
...
Sheridan
2 months ago
I think it's .cfg.json too, it's the recommended format for AEM as a Cloud Service.
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