A trigger name in SQL 2005 cannot start with #.
A
Correct answer
Explanation
Trigger names cannot begin with # or ## because those prefixes designate temporary and global temporary objects respectively. Triggers are permanent schema objects that must follow regular identifier naming rules. The # prefix is reserved for temporary tables and temporary stored procedures that are automatically cleaned up when the session ends.