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

Salesforce Exam B2C Commerce Developer Topic 13 Question 69 Discussion

Actual exam question for Salesforce's B2C Commerce Developer exam
Question #: 69
Topic #: 13
[All B2C Commerce Developer Questions]

The developer wants to be able to view DEBUG

The developer wants to be able to view DEBUG level messages for myLogCategory in the Request Log tool. Given the custom log configurations in the image above, what does the developer need to do to accomplish this?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Nieves
5 months ago
Wait, there's a 'Request Log tool'? I thought we were just supposed to use good old console.log() like the rest of us mortals.
upvoted 0 times
Leonardo
3 months ago
Maybe they should do both to make sure they can view DEBUG level messages.
upvoted 0 times
...
Valda
3 months ago
Or they could also check the DEBUG box in the Log Files section.
upvoted 0 times
...
Leonida
4 months ago
And also check the DEBUG box in the Log Files section.
upvoted 0 times
...
Domitila
4 months ago
I think the developer needs to change the Log Level for myLogCategory to DEBUG.
upvoted 0 times
...
Billy
4 months ago
I think the developer needs to change the Log Level for myLogCategory to DEBUG.
upvoted 0 times
...
Pete
4 months ago
Yeah, there's a Request Log tool for viewing DEBUG messages.
upvoted 0 times
...
Hyun
4 months ago
C) Change the Log Level for myLogCategory to DEBUG and check the DEBUG box in the Log Files section.
upvoted 0 times
...
Dannette
4 months ago
Yeah, there's a Request Log tool for viewing DEBUG messages.
upvoted 0 times
...
Alica
4 months ago
B) Check the DEBUG box in the Log Files section.
upvoted 0 times
...
Johnetta
4 months ago
A) Change the Log Level for myLogCategory to DEBUG.
upvoted 0 times
...
...
Aleshia
5 months ago
I believe option A is the correct answer because DEBUG level messages are specific to the Log Level setting.
upvoted 0 times
...
Avery
5 months ago
Haha, the developer must be a real debugging ninja to need this level of detail. Option C is the way to go, no doubt about it.
upvoted 0 times
Lizbeth
4 months ago
For sure, option C covers all the bases for viewing DEBUG level messages.
upvoted 0 times
...
Dacia
4 months ago
Definitely, the developer must be diving deep into debugging with this setup.
upvoted 0 times
...
Beatriz
5 months ago
Yeah, changing the log level and checking the DEBUG box should do the trick.
upvoted 0 times
...
Ashton
5 months ago
I agree, option C seems like the best choice here.
upvoted 0 times
...
...
Dallas
5 months ago
I agree with Laurel, changing the Log Level should do the trick.
upvoted 0 times
...
Fatima
5 months ago
I think option A is the way to go. Just changing the log level should be enough, no need to mess with the Log Files section.
upvoted 0 times
...
Arlyne
5 months ago
Definitely option C. You need to change the log level and check the debug box to view the DEBUG messages. Easy peasy!
upvoted 0 times
Verdell
4 months ago
Agreed, it's a simple solution. Just need to do both steps.
upvoted 0 times
...
Lynna
5 months ago
Option C is the way to go. Change the log level and check the debug box.
upvoted 0 times
...
...
Laurel
6 months ago
I think the developer should change the Log Level for myLogCategory to DEBUG.
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