問題文
A ticketing platform's component asks Apex for all 60,000 events in the catalog and renders them in a table. It fails in production but worked with the 300 events in the developer's scratch org. What should change?
選択肢
- Split the retrieval across 60 separate Apex methods that each return 1,000 events and call them all from the component, and no single invocation builds a large response and each limit is measured on its own.
- Have Apex return only the page of rows the table is showing, and additionally annotate the method as cacheable so the client keeps each page, which removes the heap concern because the records are then held in the browser instead of on the server.
- Raise the number of rows the component requests to the query row limit of 50,000, which is the highest number that a transaction may retrieve at once.
- Have Apex return only the page of rows the table is showing, plus the total count, because the transaction has a 6 megabyte heap and the response has to be built and transferred as well.