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.

• ✓

  Implement pagination in the Apex controller to return a limited number of records per call, and use the Lightning Web Component to request subsequent pages as needed.

  Why this is correct

  Pagination reduces the amount of data transferred in a single call, lowering heap usage and improving load times. The LWC can request pages on demand, providing a better user experience. This approach avoids hitting heap size limits and is a standard pattern for handling large datasets in Lightning.

• ✗

  Increase the heap size limit by using the @AuraEnabled annotation with the 'continuation' attribute to handle long-running requests.

  Why it's wrong here

  The 'continuation' attribute is used for asynchronous callouts, not for increasing heap size. Heap size limits are fixed and cannot be increased. Continuations are for HTTP callouts to external services, not for querying large datasets within Salesforce.

• ✗

  Use the @AuraEnabled(cacheable=true) annotation on the Apex method to cache the results on the client side.

  Why it's wrong here

  While caching can improve performance for repeated calls, it does not solve the initial problem of returning 10,000 records in one call, which may still exceed heap limits and cause slow load times. Caching is beneficial for infrequently changing data but does not address the large payload size.

• ✗

  Move the data retrieval logic to a Visualforce page and embed it in the Lightning Web Component using an iframe.

  Why it's wrong here

  Embedding a Visualforce page in an iframe is not a recommended practice for Lightning Web Components and does not inherently improve performance. It adds complexity and may still face the same heap and query limits. This approach is outdated and not a performance optimization.