What is a recommended practice for file naming conventions?

• A. Using vague or default names
• B. Describing the file and including a version
• C. Including personal identifiers in the file name
• D. Creating overly long file names

Answer: (B)

Using descriptive names along with versioning is a best practice for file naming conventions because it enhances clarity and organization. A well-structured file name makes it easier to identify the contents of the file at a glance. Including details about the type of content, subject matter, or purpose of the file can significantly aid both personal and team workflows, especially as the number of files increases.

Versioning within the name allows users to track revisions over time, reducing confusion about which file is the most current. This is particularly important in collaborative environments where multiple people might be working on similar documents or projects.

In contrast, vague or default names do not convey meaningful information and can lead to misunderstandings. Personal identifiers can compromise privacy and security, whereas overly long names can create difficulties in file management or sharing, especially across different platforms that may impose character limits or make file navigation cumbersome.