Suggested answer

Trigger firing order by operation: Insert: before insert → (validation rules, duplicates, save) → after insert. Update: before update → (validation rules, duplicates, save) → after update. If a workflow field update occurs: before update → after update fires again (once more). Delete: before delete → (save/remove from DB) → after delete. Undelete: after undelete (no before undelete). Multiple triggers on the same object for the same event fire in an undefined order — do not rely on order between multiple triggers. Use a single trigger per object with a dispatcher pattern. When a workflow rule updates a field, it re-fires before/after update triggers one more time (not recursively beyond that single re-fire). Process Builder fires after the trigger cycle.

Practice content for interview preparation; not an official vendor answer. Verify details against current product documentation.

Community comments (0)

No comments yet.

Sign in or create a free account to add a comment. Comments are moderated before they appear.

Plain text only, 3–2000 characters. A moderator reviews every comment before it is published.