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

Salesforce B2B Commerce for Developers Accredited Professional (AP-202) Exam - Topic 4 Question 3 Discussion

Which two usages of ccLog should be avoided in Salesforce B2B Commerce? (2 answers)
A) ccrz.ccLog.log(System.LoggingLevel.ERROR, 'D:something', myCallToGetMessage(pl) ), where myCallToGetMessage(pl) is a method invocation and B) crz.ccLog.log(System.LoggingLevel.WARN, 'D:something', 'Something unexpected occurred: The data we were expecting for pl was not there,')
C) crz.ccLog.log(System.LoggingLevel.DEBUG, 'D:myOrderList', myOrderList), where myOrderList is a list of orders
D) crz.ccLog.log(System.LoggingLevel.DEBUG, 'D:myOrder', myOrder), where myOrder is an order object

Salesforce B2B Commerce for Developers Accredited Professional (AP-202) Exam - Topic 4 Question 3 Discussion

Actual exam question for Salesforce's B2B Commerce for Developers Accredited Professional (AP-202) exam
Question #: 3
Topic #: 4
[All B2B Commerce for Developers Accredited Professional (AP-202) Questions]

Which two usages of ccLog should be avoided in Salesforce B2B Commerce? (2 answers)

Show Suggested Answer Hide Answer
Suggested Answer: A, B

by Margart at May 08, 2022, 10:21 PM

Limited Time Offer

25%

Off

Get Premium B2B Commerce for Developers Accredited Professional (AP-202) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Sharee
7 months ago
I’m surprised that logging an order object is discouraged!
upvoted 0 times
...
Gearldine
7 months ago
B is definitely a no-go, too vague for a warning.
upvoted 0 times
...
Antonio
7 months ago
Wait, why is C bad? It seems useful to log order lists.
upvoted 0 times
...
Lettie
8 months ago
Totally agree with A, it’s a bad practice.
upvoted 0 times
...
Tracey
8 months ago
I think A and C should be avoided. Too much info in logs!
upvoted 0 times
...
Kirk
8 months ago
I can't recall the specifics, but I think we were told to be cautious with WARN logs too. B might be risky if it exposes too much information.
upvoted 0 times
...
Erasmo
8 months ago
I'm not entirely sure, but I think logging sensitive data like order details could be a bad practice. That might make D a candidate too.
upvoted 0 times
...
Karina
8 months ago
I remember we discussed avoiding logging method invocations because it can lead to performance issues. So, maybe A is one to avoid?
upvoted 0 times
...
Freeman
8 months ago
I feel like we had a practice question about logging levels, and I think DEBUG logs should be avoided in production. So, C could be a good choice.
upvoted 0 times
...
Elsa
8 months ago
Okay, I think I've got this. The key is to use a route deployment with Automap configured and X-Forwarded-For inserted in the HTTP headers. That way, the web servers can see the actual client IP addresses.
upvoted 0 times
...
Chauncey
8 months ago
Hmm, I'm a bit confused. I'm not sure what the "supplier's perspective model" is referring to. I'll need to think this through carefully.
upvoted 0 times
...

Save Cancel