Notifications
Clear all
Topic starter
04/11/2022 4:32 pm
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?
- 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
Suggested Answer: C