Salesforce Platform Developer Practice Exam

What action can a developer take in a before update trigger?

1. Update the original object using an update DML operation.

2. Delete the original object using a delete DML operation.

3. Change field values using the Trigger.new context variable.

4. Display a custom error message in the application interface.

The correct answer is: Change field values using the Trigger.new context variable.

In a before update trigger, a developer is allowed to manipulate the records that are being updated before they are saved to the database. This is achieved using the Trigger.new context variable, which contains the new version of the records being updated. By modifying the field values within Trigger.new, the developer can ensure that specific fields are set to desired values before the update transaction is completed. This capability is essential for enforcing business rules, performing validations, or modifying data as part of the processing logic. For example, if a certain field must be adjusted based on conditions within the logic, the developer can simply modify the corresponding values in Trigger.new. The other options involve operations that are not permissible in a before update trigger context. Updating or deleting the original object through DML operations in a before update trigger would result in recursive calls and is not allowed, as it can lead to unintended consequences and performance issues. Displaying a custom error message is also not feasible directly within a trigger context; rather, error messages can be managed through exceptions thrown during validation, but this requires a different approach than simply displaying them through the trigger logic.