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 3 Question 88 Discussion

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

A custom cartridge that seemed to be performing well in a sandbox has been installed in production. The production instance is showing increased page load times that seem to be related to the new custom code. What can a developer do to quickly track down the potential problem?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Shawn
2 months ago
I bet the person who wrote option A has never actually worked in production before. It's like they're trying to add more fuel to the dumpster fire. C is the way to go, no doubt about it.
upvoted 0 times
Marg
13 days ago
I bet the person who wrote option A has never actually worked in production before. It's like they're trying to add more fuel to the dumpster fire. C is the way to go, no doubt about it.
upvoted 0 times
...
Murray
15 days ago
C) Use the Code Profiler in a sandbox instance. Set the mode Extended Development Mode and then load the suspected pages and run the suspected process several times. Click the refresh button to see the new data.
upvoted 0 times
...
Toshia
16 days ago
B) Use the Code Profiler in production instance. Set the mode to Development Mode and click the refresh button to see the new mode displayed.
upvoted 0 times
...
Art
19 days ago
A) Use the Code Profiler in production instance. Set the mode to Development Mode and then wait a few minutes to collect data from onsite traffic. Click the refresh button to see the new data.
upvoted 0 times
...
German
23 days ago
It's better to be safe than sorry when it comes to making changes in production.
upvoted 0 times
...
Winfred
1 months ago
I always test things out in a sandbox before touching production.
upvoted 0 times
...
Daron
1 months ago
Yeah, using the Code Profiler in a sandbox first is definitely the safer route.
upvoted 0 times
...
Geoffrey
2 months ago
I agree, option A sounds like a disaster waiting to happen.
upvoted 0 times
...
...
Vincenza
2 months ago
That's a good point, Jillian. It might be helpful to test in the sandbox before making changes in production.
upvoted 0 times
...
Jillian
2 months ago
I prefer option C, using the Code Profiler in a sandbox instance first to narrow down the issue.
upvoted 0 times
...
Maryanne
3 months ago
Hold up, did they really think we'd fall for using the Code Profiler in production? That's like trying to fix a leaky faucet by hitting it with a sledgehammer. C is the only sensible choice.
upvoted 0 times
...
Latosha
3 months ago
I agree with you, Vincenza. Setting the mode to Development Mode can help track down the problem quickly.
upvoted 0 times
...
Carissa
3 months ago
Hmm, I'm not sure about setting the mode to Development Mode in production. That sounds like a good way to bring the whole site down. C is the clear winner here.
upvoted 0 times
...
Norah
3 months ago
Ah, the age-old problem of production issues. Using the Code Profiler in production is risky, we don't want to slow down the site even more. C is the way to go - sandbox testing is the safest bet.
upvoted 0 times
Salome
1 months ago
C) Use the Code Profiler in a sandbox instance. Set the mode Extended Development Mode and then load the suspected pages and run the suspected process several times. Click the refresh button to see the new data.
upvoted 0 times
...
Karol
2 months ago
B) Use the Code Profiler in production instance. Set the mode to Development Mode and click the refresh button to see the new mode displayed.
upvoted 0 times
...
Lina
2 months ago
A) Use the Code Profiler in production instance. Set the mode to Development Mode and then wait a few minutes to collect data from onsite traffic. Click the refresh button to see the new data.
upvoted 0 times
...
...
Vincenza
3 months ago
I think the best option is to use the Code Profiler in production instance.
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