Salesforce Exam B2C Commerce Developer Topic 3 Question 88 Discussion

Actual exam question for Salesforce's B2C Commerce Developer exam

Question #: 88
Topic #: 3

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?

AUse 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.

BUse the Code Profiler in production instance. Set the mode to Development Mode and click the refresh button to see the new mode displayed.

CUse 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.

Show Suggested Answer

Suggested Answer: A

by Yoko at Mar 20, 2025, 03:06 PM

Limited Time Offer

25%

Off

Get Premium B2C Commerce Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Shawn

16 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

Geoffrey

4 days ago

I agree, option A sounds like a disaster waiting to happen.

upvoted 0 times

...

Vincenza

17 days 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

19 days ago

I prefer option C, using the Code Profiler in a sandbox instance first to narrow down the issue.

upvoted 0 times

...

Maryanne

24 days 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

26 days ago

I agree with you, Vincenza. Setting the mode to Development Mode can help track down the problem quickly.

upvoted 0 times

...

Carissa

26 days 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

27 days 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

Lina

16 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

...

Vincenza

1 months ago

I think the best option is to use the Code Profiler in production instance.

upvoted 0 times

...