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 inside a for loop to retrieve each Account and update it immediately.

  Why it's wrong here

  Querying inside a for loop is a classic anti-pattern that leads to hitting the SOQL query limit (100 queries) when processing 200 Cases. It also increases CPU time and can cause the trigger to fail. This approach does not scale and should be avoided in favor of bulkified logic.

• ✗

  Use a Map to store the Accounts from Trigger.new, but query the Accounts in the trigger's constructor.

  Why it's wrong here

  Triggers do not have a constructor; they are executed as a single unit. The concept of a constructor is not applicable. The correct approach is to query in the trigger body before the loop, not in a constructor. This option is misleading and technically incorrect for Apex triggers.

• ✓

  Use a single SOQL query to retrieve all related Accounts based on the AccountId values from Trigger.new, then use a Map to update the Accounts.

  Why this is correct

  Collecting all AccountId values from Trigger.new and performing one SOQL query to retrieve the related Accounts is the best practice for bulkification. Using a Map to relate Accounts to Cases allows efficient updates without additional queries. This approach ensures the trigger can handle up to 200 records within governor limits, reducing the number of queries to one.

• ✗

  Use a Database.query call with a bind variable for each AccountId to retrieve the Accounts in a single query.

  Why it's wrong here

  While using Database.query with a bind variable is possible, it is not necessary and adds complexity. A static SOQL query with a WHERE clause using the IN operator on a collection of AccountIds is simpler and more efficient. Database.query is typically used for dynamic queries, but here a static query is sufficient and easier to maintain.