SF-PD2 Performance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use JavaScript Remoting to load all records asynchronously after the page renders.

  Why it's wrong here

  JavaScript Remoting can improve perceived performance by loading data asynchronously, but it still transfers all records to the client, which can be slow and may hit other limits. It does not reduce the amount of data processed, and the initial page load might still be heavy if the data is large.

• ✗

  Set the readOnly attribute of the <apex:page> component to true.

  Why it's wrong here

  Setting readOnly to true can improve performance by reducing view state and allowing more query rows, but it does not reduce the number of records loaded. For thousands of line items, the page would still render all records, leading to slow load times. Pagination is more effective for large data sets.

• ✗

  Increase the view state limit by contacting Salesforce support to raise the limit.

  Why it's wrong here

  View state limit is 170 KB for Visualforce pages and cannot be increased by support. Exceeding it causes an error. This is not a viable performance optimization; it would not solve the underlying issue of large data volume.

• ✓

  Implement pagination using a StandardSetController to limit the number of records displayed per page.

  Why this is correct

  StandardSetController supports pagination and reduces the number of records loaded and rendered at once. This decreases view state size and improves page load time. It is a standard approach for handling large data sets in Visualforce without major UI changes.