問題文
A nonprofit imports year-end donations in batches of 5,000 rows. Partway through one batch an Apex trigger exceeds a governor limit. The operations team assumed the rows processed before the failure were saved, and they are re-running only the remainder. What actually happened to the data?
選択肢
- Nothing from that batch was committed, because exceeding a limit throws a run-time exception that can't be handled and the whole transaction is rolled back to the state before it began.
- The rows processed before the failure were saved and the rest were skipped; the operations team can restart the load from the exact row where it happened to stop during the run last night.
- The platform automatically retried the failed portion in a separate transaction with the asynchronous limits, so the remaining rows were eventually written and re-running the batch now creates duplicates.
- The rows were saved but the trigger's changes to related records were discarded; the donations now exist while the summary fields on the related campaigns were left untouched by the run.