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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E706 Topic 8 Question 17 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 17
Topic #: 8
[All AD0-E706 Questions]

You are debugging an issue with an extension that only occurs in Production. The extension writes relevant information using the debug log level

However that specific information is not getting written to the logs on Production

How do you fix this>

Show Suggested Answer Hide Answer
Suggested Answer: C

by Arthur at Jul 27, 2022, 03:20 PM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Precious
13 days ago
Option D is the way to go, my friends. Enabling debug logging in the Admin interface is like having a superpower - you can see all the secrets of the production system without having to get your hands dirty!
upvoted 0 times
...
Julieta
14 days ago
Ah, the joys of debugging production issues! Option A sounds tempting, but enabling developer mode in production is a bit like putting a bandaid on a broken leg. It's a quick fix, but it's not really a long-term solution.
upvoted 0 times
Helga
3 days ago
B) Write a custom logger that writes the debug information to var/log/custom, log
upvoted 0 times
...
...
Whitley
29 days ago
I'm leaning towards option B. Writing a custom logger that writes the debug information to a separate log file sounds like a more robust solution, especially if you need to keep the debug logging enabled for a longer period of time.
upvoted 0 times
Nu
3 days ago
A) That could work, but I think option B is more reliable in the long run
upvoted 0 times
...
Laura
4 days ago
B) Write a custom logger that writes the debug information to var/log/custom, log
upvoted 0 times
...
Vallie
19 days ago
A) Enable developer mode in Production for a short period to gather the required information
upvoted 0 times
...
...
Ariel
1 months ago
Option C seems like a good idea, but I'm not sure if it's the best solution. Enabling debug logging in the config file and then deploying it to Production could be risky, especially if you forget to turn it off later.
upvoted 0 times
Doyle
2 days ago
B) Write a custom logger that writes the debug information to var/log/custom, log
upvoted 0 times
...
Eladia
19 days ago
A) Enable developer mode in Production for a short period to gather the required information
upvoted 0 times
...
...
Narcisa
2 months ago
That's a good point, Margery. Option B could be a better solution for this issue.
upvoted 0 times
...
Margery
2 months ago
I disagree, I believe option B is more efficient. Writing a custom logger will ensure the debug information is stored in a specific location.
upvoted 0 times
...
Narcisa
2 months ago
I think option A is the best choice. Enabling developer mode in Production will help gather the required information.
upvoted 0 times
...
Delfina
2 months ago
I think option D is the way to go. Enabling debug logging in the Admin interface is the easiest and most straightforward way to get the required information without having to mess with the code or deployment process.
upvoted 0 times
Elke
2 hours ago
C) Enable debug logging in app/etc/config.php locally and deploy it to Production
upvoted 0 times
...
Tayna
8 days ago
B) Write a custom logger that writes the debug information to var/log/custom, log
upvoted 0 times
...
Jacquelyne
13 days ago
A) Enable developer mode in Production for a short period to gather the required information
upvoted 0 times
...
...

Save Cancel