SF-PD2 Performance Practice Question
Exhibit
14:22:05.054 (54201234)|CUMULATIVE_LIMIT_USAGE 14:22:05.054 (54201234)|LIMIT_USAGE_FOR_NS|(default)| Number of SOQL queries: 15 out of 100 Number of query rows: 1200 out of 50000 Maximum CPU time: 10005 out of 10000 *CLOSE TO LIMIT* Maximum heap size: 2500 out of 6000000
Refer to the exhibit. A developer is reviewing a debug log for a failed transaction. What is the primary performance issue identified in the log snippet?
⚠ Common exam trap
Candidates often mistake CPU limit errors for SOQL query limit errors, failing to distinguish between the 10,000 ms execution time limit and the 100 query limit.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The transaction failed because the CPU time exceeded the 10,000 ms limit.
The debug log shows the cumulative limit usage at the end of a transaction. The 'Maximum CPU time' entry indicates that 10,005 milliseconds were used, which exceeds the synchronous governor limit of 10,000 milliseconds. This results in a LimitException, and the transaction is rolled back, regardless of how many queries or rows were processed.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The transaction failed due to too many SOQL queries being executed.
Why it's wrong here
The log shows only 15 SOQL queries were executed out of a limit of 100. This is well within the acceptable range for a single transaction. The failure is not related to query volume, but rather to the amount of time the CPU spent processing logic, as indicated by the CPU time limit usage.
- ✗
The transaction failed because the heap size limit was exceeded during processing.
Why it's wrong here
The heap size usage is reported as 2,500 bytes out of a 6,000,000 byte limit. This is a negligible amount of memory usage. The error in the log specifically points to the CPU time, not memory exhaustion. Developers must distinguish between these two separate resource limits when debugging performance issues.
- ✓
The transaction failed because the CPU time exceeded the 10,000 ms limit.
Why this is correct
The log explicitly states that the Maximum CPU time was 10,005 milliseconds, which is over the 10,000 ms synchronous limit. The '*CLOSE TO LIMIT*' or actual exceeding of the number causes a LimitException. This means the code spent too long executing logic, loops, or transformations, causing the platform to terminate the request.
- ✗
The transaction failed because the number of query rows exceeded 50,000.
Why it's wrong here
The log shows that only 1,200 query rows were retrieved out of the 50,000 allowed. This is a very small percentage of the total allowed rows. Therefore, the data volume retrieved via SOQL is not the cause of this specific failure; the focus should remain on the CPU time limit instead.
Visual reference
About these practice questions
This SF-PD2 question is part of Courseiva's 226-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-PD2 practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-PD2 exam.