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

Salesforce Exam B2C Commerce Developer Topic 4 Question 62 Discussion

Actual exam question for Salesforce's B2C Commerce Developer exam
Question #: 62
Topic #: 4
[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:

Paulina
10 months ago
C is the correct answer. You need to do both steps to view the DEBUG level messages for myLogCategory.
upvoted 0 times
...
Cristy
10 months ago
Haha, this question is a classic! The answer is definitely C. Gotta love those double-whammy solutions, am I right?
upvoted 0 times
Lettie
10 months ago
Absolutely, C covers all the bases with changing the log level and checking the DEBUG box.
upvoted 0 times
...
Evangelina
10 months ago
I agree, C is the way to go for sure.
upvoted 0 times
...
...
Fernanda
10 months ago
I see your point, So maybe the correct answer is to change the Log Level for myLogCategory to DEBUG and also check the DEBUG box in the Log Files section.
upvoted 0 times
...
Daniela
11 months ago
But shouldn't the developer also check the DEBUG box in the Log Files section to ensure all bases are covered?
upvoted 0 times
...
Erick
11 months ago
Option C is the way to go. You need to set the Log Level to DEBUG and also make sure the DEBUG box is checked in the Log Files section.
upvoted 0 times
Tora
10 months ago
I agree. It ensures that DEBUG level messages for myLogCategory will be visible in the Request Log tool.
upvoted 0 times
...
Natalie
10 months ago
That makes sense. It's important to have both settings configured correctly.
upvoted 0 times
...
Elena
10 months ago
Option C is the way to go. You need to set the Log Level to DEBUG and also make sure the DEBUG box is checked in the Log Files section.
upvoted 0 times
...
...
Oren
11 months ago
I think the answer is C. Changing the Log Level for myLogCategory to DEBUG and checking the DEBUG box in the Log Files section should do the trick.
upvoted 0 times
Janine
10 months ago
Yes, changing the Log Level and checking the DEBUG box should give us the DEBUG level messages.
upvoted 0 times
...
Holley
10 months ago
I agree, option C seems like the right choice.
upvoted 0 times
...
Gregoria
10 months ago
Yes, that's correct. It's important to do both to view DEBUG level messages.
upvoted 0 times
...
Lorrie
11 months ago
I agree, changing the Log Level to DEBUG and checking the DEBUG box should work.
upvoted 0 times
...
...
Audry
11 months ago
I agree with That seems like the right step to accomplish viewing DEBUG level messages.
upvoted 0 times
...
Lauran
11 months ago
I think the developer needs to change the Log Level for myLogCategory to DEBUG.
upvoted 0 times
...
Paris
12 months ago
I think Geoffrey might be right, it could be a combination of changing the Log Level and checking the DEBUG box.
upvoted 0 times
...
Geoffrey
12 months ago
Actually, I believe the developer should check the DEBUG box in the Log Files section.
upvoted 0 times
...
Effie
1 years ago
I agree with Audria, changing the Log Level should do the trick.
upvoted 0 times
...
Audria
1 years ago
I think the developer needs to 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