What is a best practice for naming attachments?

What is a best practice for naming attachments?

• A. Label attachments with generic names like 'Document' or 'File'.
• B. Use descriptive names that reflect content, avoid spaces or special characters, and include dates if relevant.
• C. Always rename attachments to random strings.
• D. Include the recipient's name in the file name.

Answer: (B)

Descriptive, safe naming of attachments makes it clear what the file is, helps recipients find and reference it later, and avoids compatibility issues. The best practice is to use names that reflect the content, such as a project or document type plus a date when relevant (for example, Budget_Q2_2024.pdf). This communicates exactly what the attachment contains and supports quick searching. Avoid spaces or special characters because some systems and email clients don’t handle them well; using underscores or hyphens keeps names readable and portable. If a date is relevant, including it helps with versioning and organizing multiple files over time. Keep names concise but informative to prevent truncation or confusion. Other approaches fall short because generic labels like “Document” or “File” don’t reveal content, and random strings provide no context. Including the recipient’s name isn’t necessary for organization and can raise privacy or redundancy issues.

Descriptive, safe naming of attachments makes it clear what the file is, helps recipients find and reference it later, and avoids compatibility issues. The best practice is to use names that reflect the content, such as a project or document type plus a date when relevant (for example, Budget_Q2_2024.pdf). This communicates exactly what the attachment contains and supports quick searching. Avoid spaces or special characters because some systems and email clients don’t handle them well; using underscores or hyphens keeps names readable and portable. If a date is relevant, including it helps with versioning and organizing multiple files over time. Keep names concise but informative to prevent truncation or confusion. Other approaches fall short because generic labels like “Document” or “File” don’t reveal content, and random strings provide no context. Including the recipient’s name isn’t necessary for organization and can raise privacy or redundancy issues.