Salesforce Certified Platform Developer II — Question 78

A developer receives a LimitException: Too many query rows: 50001 error when running code.
What debugging approach using the Developer Console provides the fastest and most accurate mechanism to identify a specific component that may be returning an unexpected number of rows?

Answer options

• A. Count the number of Row Limit warning messages in the Debug Logs
• B. Add System.debug(System.getQueryRows()) to the code to track SOQL usage
• C. Filter the Debug Log on SOQL_EXECUTE_END statements to track the results of each SOQL Query
• D. Use the Execution Overview to see the number of rows returned by each Executed Unit

Correct answer: C

Explanation

The correct answer is C because filtering the Debug Log on SOQL_EXECUTE_END statements allows the developer to see the results of each SOQL query executed, directly identifying which query is returning an excessive number of rows. Option A is incorrect as counting Row Limit warnings does not provide specific information on the queries. Option B, while useful, does not pinpoint the exact source of the row limit issue as effectively as option C. Option D provides an overview but is less direct than filtering the Debug Log.