Which statement reflects best practice for triggered send definitions?

• A. Reuse a single definition for all types
• B. Clone and publish after each change
• C. Use unique definitions for different send types and publish anytime you make changes
• D. Avoid pausing a triggered send

Answer: (C)

Triggered send definitions should be kept separate for each type of send you’re handling. Having unique definitions for different send types lets you tailor the content, audience, and triggering mechanism precisely, keeps testing and governance clear, and makes reporting accurate. When you adjust a definition, publish the changes so they take effect right away and new sends use the updated settings instead of sticking with an older version. Reusing one definition across multiple send types creates the risk of sending the wrong content to the wrong audience and makes management and auditing more difficult. Cloning definitions after every change adds unnecessary clutter and complexity, while pausing a triggered send isn’t inherently required for good practice—pausing can be used in some scenarios, but it’s not the standard mechanism described here.