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 Advanced-Administrator Topic 11 Question 78 Discussion

Actual exam question for Salesforce's Salesforce Certified Advanced Administrator exam
Question #: 78
Topic #: 11
[All Salesforce Certified Advanced Administrator Questions]

Cloud Kicks users report receiving an "Apex CPU time limit exceeded" error message when attempting to close certain opportunity records. This does not occur on every opportunity record change or for every user.

What is the recommended method for the administrator to identify the cause?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Shelton
2 months ago
True, reviewing the Setup Audit Trail can help in tracking down any recent changes that might be affecting the CPU limits.
upvoted 0 times
...
Gerald
2 months ago
I believe reviewing the Setup Audit Trail could also give insights into what changes are causing the error.
upvoted 0 times
...
Abel
2 months ago
That's a good point, Shelton. Monitoring with Login Forensics can also be helpful in identifying the issue.
upvoted 0 times
...
Shelton
2 months ago
I personally prefer setting up Apex Exception Email alerts, as it provides real-time notification of errors.
upvoted 0 times
...
Gerald
2 months ago
I agree with Abel, Debug Logging can help pinpoint the cause of the CPU time limit exceeded error.
upvoted 0 times
...
Abel
3 months ago
I think the administrator should enable Debug Logging for users.
upvoted 0 times
...
Rosenda
3 months ago
I believe that monitoring with Login Forensics could also provide valuable insights on the issue.
upvoted 0 times
...
Ilene
3 months ago
Option C? Nah, that's like trying to find a needle in a haystack. B or D are definitely the way to go here, if you ask me.
upvoted 0 times
Marisha
2 months ago
I agree, getting alerts for exceptions could really help in this situation.
upvoted 0 times
...
Salome
2 months ago
D) Set up Apex Exception Email alerts
upvoted 0 times
...
Sharee
2 months ago
Yeah, that sounds like a good idea. It could help pinpoint the issue.
upvoted 0 times
...
Ellsworth
3 months ago
B) Enable Debug Logging for users.
upvoted 0 times
...
...
Susy
3 months ago
But wouldn't setting up Apex Exception Email alerts also be helpful in identifying the cause?
upvoted 0 times
...
Keena
3 months ago
I bet the admin wishes they had a crystal ball to see what's going on. Option B might be the closest thing to that, though.
upvoted 0 times
Jarod
2 months ago
C) Review the Setup Audit Trail.
upvoted 0 times
...
Margery
3 months ago
B) Enable Debug Logging for users.
upvoted 0 times
...
Isaac
3 months ago
C) Review the Setup Audit Trail.
upvoted 0 times
...
Cordie
3 months ago
B) Enable Debug Logging for users.
upvoted 0 times
...
Kiley
3 months ago
A) Monitor with Login Forensics.
upvoted 0 times
...
...
Essie
4 months ago
Hmm, I'm torn between B and D. Both seem like viable options, but I'm curious if anyone has a funny anecdote about a time they had to debug a similar issue.
upvoted 0 times
Jose
3 months ago
I agree, setting up Apex Exception Email alerts could also help in this situation.
upvoted 0 times
...
Jonell
3 months ago
I think enabling Debug Logging for users would be the best option to identify the cause.
upvoted 0 times
...
...
Paris
4 months ago
I'd go with D. Setting up Apex Exception Email alerts could give the admin a heads-up on the problem and point them in the right direction.
upvoted 0 times
Kami
3 months ago
That sounds like a good idea. It could help pinpoint the issue quickly.
upvoted 0 times
...
Steffanie
3 months ago
D) Set up Apex Exception Email alerts
upvoted 0 times
...
...
Azzie
4 months ago
Option B sounds like the way to go. Enabling debug logging can help pinpoint the issue, especially since it's not happening for all records or users.
upvoted 0 times
Lavelle
3 months ago
Setting up email alerts for Apex exceptions could also be a proactive way to catch any issues before they escalate.
upvoted 0 times
...
Marva
3 months ago
D) Set up Apex Exception Email alerts
upvoted 0 times
...
Rodrigo
3 months ago
I think reviewing the Setup Audit Trail could also help identify any recent changes that might be causing the issue.
upvoted 0 times
...
Delsie
3 months ago
C) Review the Setup Audit Trail.
upvoted 0 times
...
Theresia
4 months ago
That's a good point. Debug logging can provide more detailed information on what's causing the error.
upvoted 0 times
...
Jillian
4 months ago
B) Enable Debug Logging for users.
upvoted 0 times
...
...
Isaiah
4 months ago
I agree, Debug Logging can track the CPU usage and help pinpoint the issue.
upvoted 0 times
...
Johana
4 months ago
I think the administrator should enable Debug Logging for users to identify the cause.
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