When does a validation rule evaluate its formula and potentially block a record from being saved?
- AWhen the record is saved, whether the save comes from the UI, the API, or a data import, if the formula evaluates to true. Correct
- BOnly when a user edits the record manually through a Lightning record page, not during any automated process.
- CAfter the record is committed to the database, so the record saves first and the error appears on the next edit.
- DOnly during Data Loader operations, because the UI relies on required-field settings instead of validation rules.
Why A is correct: Validation rules run on every save regardless of source, and the record is blocked when the formula returns true, so this correctly states both the timing and the trigger condition.
Why B is wrong: It is tempting to think validation only guards manual edits, but rules also fire on API and automation-driven saves, so limiting them to manual edits is wrong.
Why C is wrong: This misplaces the timing: validation runs before commit and stops the save outright, rather than allowing the record to save and surfacing an error later.
Why D is wrong: Validation rules apply to UI saves as well as Data Loader, and required-field settings are a separate control, so restricting rules to Data Loader is incorrect.