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 SOQL query with a subquery to retrieve related records for all trigger records in one query, then process the results in the loop.

  Why it's wrong here

  Using a subquery can retrieve related records in one query, but it is not always possible, especially for complex relationships. Moreover, the subquery approach may still require additional processing. The most reliable bulkification pattern is to query all related records in one query using a WHERE clause with the trigger record IDs and then map them.

• ✗

  Use a SOQL query with a WHERE clause that filters by the trigger records' IDs, and then loop through the results to update each record.

  Why it's wrong here

  While filtering by IDs is good, if the query is still inside the loop, it remains inefficient. The key is to move the query outside the loop entirely. Looping through results to update each record individually can also lead to inefficient DML operations.

• ✗

  Use a SOQL query for each record but add a LIMIT clause to reduce the number of rows returned.

  Why it's wrong here

  Adding a LIMIT clause does not solve the fundamental issue of performing a query inside a loop. Each query still counts against governor limits, and the trigger will still fail for large batches. Bulkification is required to avoid this.

• ✓

  Move the SOQL query outside the loop and use a Map to correlate related records with the trigger records.

  Why this is correct

  Bulkifying the SOQL query by moving it outside the loop and using a Map to associate related records with the trigger records is the standard best practice. This reduces the number of queries to one, avoiding governor limits and improving performance.