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 a StandardSetController to enable pagination and reduce the number of records displayed per page.

  Why this is correct

  StandardSetController provides built-in pagination, allowing the page to display a subset of records at a time. This reduces the initial query size and the amount of data rendered, significantly improving load time. It also handles sorting and navigation efficiently, making it ideal for large data sets in Visualforce.

• ✗

  Add a rendered attribute to the table to conditionally display it after the page loads.

  Why it's wrong here

  Using a rendered attribute does not reduce the initial query or data retrieval; the controller still queries all 1,000 Contacts in the constructor. The table may be hidden initially, but the data is still loaded and processed, so performance remains poor. This approach does not address the root cause of slow loading.

• ✗

  Increase the view state by storing all Contacts in a transient variable.

  Why it's wrong here

  Transient variables reduce view state size but do not affect the query or rendering time. The controller still retrieves all 1,000 Contacts, and the page still renders them, so load time is not improved. Transient variables are useful for reducing view state limits, but they do not solve performance issues related to large data retrieval.

• ✗

  Use JavaScript remoting to load the Contacts asynchronously after the page renders.

  Why it's wrong here

  JavaScript remoting can improve perceived performance by loading data after the initial page render, but it still requires querying all 1,000 Contacts and transferring them to the client. This may not reduce overall load time and adds complexity. It does not address the fundamental issue of querying and rendering a large number of records at once.