Which two operations affect the number of times a trigger can fire? Choose 2 answers

A trigger can be fired multiple times in a single transaction if a record update occurs after the initial DML operation. A roll-up summary field on a parent object is recalculated and updated when a child record is modified. This update on the parent is a DML operation that fires the parent object's triggers. Similarly, an after-save record-triggered flow can be configured to perform a field update on the same record that initiated the flow. This action is a subsequent DML update that will cause the triggers on that object to run again.

A. Criteria-based sharing rule calculations run after the save but do not perform a DML update on the record itself, so they do not re-fire triggers.

B. Sending an email is an action that does not cause a DML update on the record, and therefore does not cause triggers to fire again.

1. Salesforce Developer Documentation, Apex Developer Guide, "Triggers and Order of Execution". Step 14 (for after triggers) and Step 8 (for before triggers) mention that roll-up summary field updates can cause the entire save procedure to be repeated.

2. Salesforce Help, Salesforce Order of Execution. This document explicitly lists "Executes record-triggered flows that are configured to run after the record is saved" as a step that can cause the entire save process, including triggers, to restart.

3. Salesforce Architects, Record-Triggered Automation Decision Guide. This guide details how different automation tools interact, noting that after-save flows can re-trigger the save order. Section: "Order of Execution".