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 @future methods for every database update.

  Why it's wrong here

  Using @future for every update is excessive and can lead to reaching the limit for asynchronous calls. It creates a 'fire and forget' pattern that lacks the monitoring capabilities needed for complex tasks. It is best used for specific, isolated operations rather than as a general-purpose design pattern.

• ✓

  Use Queueable Apex to offload complex tasks to the background.

  Why this is correct

  Queueable Apex provides a robust way to chain and monitor asynchronous jobs. It is more flexible than @future methods and is the recommended approach for offloading non-critical, long-running operations, keeping the UI responsive while ensuring the backend work is completed reliably and in the correct order.

• ✗

  Use Platform Events to perform synchronous calculations.

  Why it's wrong here

  Platform Events are for event-driven architectures and asynchronous communication, not for synchronous calculations. They introduce a layer of decoupling that is unnecessary for simple UI responsiveness and would actually increase latency if used for immediate computation requirements, failing to improve the user's perception of application speed.

• ✗

  Write the logic in JavaScript to execute on the client side.

  Why it's wrong here

  Client-side processing is limited by the browser's capabilities and security restrictions. Large computations would freeze the browser, making the interface completely unresponsive. Complex business logic should always be handled on the server side in Apex to ensure security, data integrity, and consistent performance across all platforms.