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-E127 Topic 3 Question 20 Discussion

Actual exam question for Adobe's AD0-E127 exam
Question #: 20
Topic #: 3
[All AD0-E127 Questions]

Which node type is used by an AEM Forms developer to create a custom logger using the CRXDE Lite tool?

Show Suggested Answer Hide Answer
Suggested Answer: A

This is the node type that an AEM Forms developer needs to use to create a custom logger using the CRXDE Lite tool. The sling:OsgiConfig node type represents an OSGi configuration that can be used to configure various services and components in AEM. To create a custom logger, the developer needs to create a sling:OsgiConfig node under /apps/system/config with properties such as log.level, log.file, and log.pattern.


Contribute your Thoughts:

Noemi
2 months ago
A) sling:OsgiConfig makes sense to me because it is commonly used for custom logging in AEM Forms.
upvoted 0 times
...
Mattie
3 months ago
I've heard that some developers prefer B) sling:UgmiControl for creating custom loggers.
upvoted 0 times
...
Audria
3 months ago
I'm not sure, but I believe C) sling:NewAccess could also be a possibility.
upvoted 0 times
...
Alishia
3 months ago
I think the correct answer is A) sling:OsgiConfig.
upvoted 0 times
...
Royce
3 months ago
Based on our discussion, I feel more confident that the answer is A) sling:OsgiConfig.
upvoted 0 times
...
Xochitl
3 months ago
I think I'll go with B) sling:UgmiControl, it sounds familiar to me.
upvoted 0 times
...
Mirta
4 months ago
I agree with Royce, A) sling:OsgiConfig makes sense for creating a custom logger.
upvoted 0 times
...
Tammara
4 months ago
I remember reading about it, and I think it's C) sling:NewAccess.
upvoted 0 times
...
Levi
4 months ago
I'm not sure, but I believe it might be B) sling:UgmiControl.
upvoted 0 times
...
Royce
4 months ago
I think the answer is A) sling:OsgiConfig.
upvoted 0 times
...
Jaime
5 months ago
Ooh, a tricky one! I like it. Personally, I'm leaning towards A) sling:OsgiConfig. Seems like the most logical choice, given that we're talking about creating a custom logger. But you know what they say - when in doubt, go with sling:UgmiControl. It's the new black, or something like that.
upvoted 0 times
...
Ludivina
5 months ago
Seriously? sling:UgmiControl? I think you've been spending too much time in the AEM version of the Upside Down, my friend. Clearly the answer is A) sling:OsgiConfig. I mean, it's right there in the documentation. Unless, of course, the exam writers are trying to trick us...
upvoted 0 times
...
Peggie
5 months ago
Ah, the old custom logger conundrum. I remember struggling with this one during my certification prep. I think Jina is on the right track - sling:OsgiConfig is definitely the way to go. Unless, of course, you're feeling adventurous and want to try sling:UgmiControl. I hear that's all the rage these days. *wink wink*
upvoted 0 times
Domingo
4 months ago
I think sling:UgmiControl might be worth exploring as well.
upvoted 0 times
...
Muriel
4 months ago
I agree with you, sling:OsgiConfig is the best choice for creating a custom logger.
upvoted 0 times
...
...
Jina
5 months ago
You know, I was just reading up on this the other day. I'm pretty confident the answer is A) sling:OsgiConfig. That's the node type you use to create custom OSGi configurations, which is what you'd need to do to set up a custom logger. At least, that's what the documentation says.
upvoted 0 times
...
Willie
5 months ago
Hmm, I'm not so sure about that. Isn't sling:OsgiConfig used for configuring OSGi services? I thought we'd use something more specific to logging, like a sling:LoggerConfig or something. Anyone know for sure?
upvoted 0 times
...
Janae
5 months ago
Ah, the age-old question - how to create a custom logger in AEM Forms? This is definitely a tricky one. I think the answer is A) sling:OsgiConfig, but I'm not 100% sure. Anyone else have any thoughts?
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