Database triggers are designed for centralized operations and ensuring related actions occur. They should not duplicate built-in constraints or other triggers. Option C describes enforcing related actions (e.g., audit logging on update). Option D describes global operations firing regardless of user.