Salesforce Exam Advanced Administrator Topic 11 Question 78 Discussion

Actual exam question for Salesforce's Advanced Administrator exam

Question #: 78
Topic #: 11

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?

AMonitor with Login Forensics.

BEnable Debug Logging for users.

CReview the Setup Audit Trail.

DSet up Apex Exception Email alerts

Show Suggested Answer

Suggested Answer: B

Debug logs capture database operations, system processes, and errors that occur when executing a transaction or running unit tests. Debug logs can help identify the cause of Apex CPU time limit exceeded errors by showing the execution time of each Apex statement and trigger. Reference: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_debugging_debug_logs.htm

by Ruthann at Feb 13, 2024, 06:30 PM

Limited Time Offer

25%

Off

Get Premium Advanced Administrator Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Shelton

5 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

5 months ago

I believe reviewing the Setup Audit Trail could also give insights into what changes are causing the error.

upvoted 0 times

...

Abel

5 months ago

That's a good point, Shelton. Monitoring with Login Forensics can also be helpful in identifying the issue.

upvoted 0 times

...

Shelton

6 months ago

I personally prefer setting up Apex Exception Email alerts, as it provides real-time notification of errors.

upvoted 0 times

...

Gerald

6 months ago

I agree with Abel, Debug Logging can help pinpoint the cause of the CPU time limit exceeded error.

upvoted 0 times

...

Abel

6 months ago

I think the administrator should enable Debug Logging for users.

upvoted 0 times

...

Rosenda

6 months ago

I believe that monitoring with Login Forensics could also provide valuable insights on the issue.

upvoted 0 times

...

Ilene

6 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

5 months ago

I agree, getting alerts for exceptions could really help in this situation.

upvoted 0 times

...

Salome

5 months ago

D) Set up Apex Exception Email alerts

upvoted 0 times

...

Sharee

5 months ago

Yeah, that sounds like a good idea. It could help pinpoint the issue.

upvoted 0 times

...

Ellsworth

6 months ago

B) Enable Debug Logging for users.

upvoted 0 times

...

Susy

6 months ago

But wouldn't setting up Apex Exception Email alerts also be helpful in identifying the cause?

upvoted 0 times

...

Keena

6 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

6 months ago

C) Review the Setup Audit Trail.

upvoted 0 times

...

Margery

6 months ago

B) Enable Debug Logging for users.

upvoted 0 times

...

Isaac

6 months ago

C) Review the Setup Audit Trail.

upvoted 0 times

...

Cordie

6 months ago

B) Enable Debug Logging for users.

upvoted 0 times

...

Kiley

6 months ago

A) Monitor with Login Forensics.

upvoted 0 times

...

Essie

7 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