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.

• ✓

  Move the SOQL query outside the loop and use a Map to correlate Contacts to Accounts.

  Why this is correct

  This approach eliminates redundant queries by fetching all Contacts in a single query and then using a Map keyed by AccountId to efficiently associate them with each Account. It reduces the number of SOQL queries from potentially thousands to one, avoiding governor limits and dramatically improving page load time.

• ✗

  Add a LIMIT clause to the SOQL query inside the loop to reduce the number of records returned per Account.

  Why it's wrong here

  Adding a LIMIT reduces the number of records per query but still executes a query for each Account iteration. The total number of SOQL queries remains high, potentially exceeding governor limits and causing slow performance. It does not address the core issue of querying inside a loop.

• ✗

  Use Database.getQueryLocator to handle the Contacts and bind the result to the page.

  Why it's wrong here

  Database.getQueryLocator is useful for large data sets in batch Apex or Visualforce with pagination, but it does not directly address the issue of querying inside a loop. It would require significant refactoring and may not be suitable for displaying a fixed list of 2,000 Contacts on a single page.

• ✗

  Replace the SOQL query with a SOSL search to retrieve all Contacts at once.

  Why it's wrong here

  SOSL is designed for text-based searches across multiple objects, not for retrieving all child records for a given parent. Using SOSL here would be inefficient and may not return all Contacts. It also does not solve the loop query problem because SOSL would still be called repeatedly if left inside the loop.