Which naming convention practices facilitate collaboration and version control?

• A. Name assets informally without a naming convention.
• B. Use consistent naming, avoid spaces, use prefixes/suffixes for types, include version identifiers, and maintain an organized folder structure.
• C. Allow spaces in names and rely on folders only.
• D. Never version control asset names.

Answer: (B)

Having a consistent naming system and an organized folder structure makes collaboration and version control reliable. When assets follow a predictable naming pattern, team members can quickly understand what an asset is, where it fits in the project, and how it relates to others, which reduces miscommunication and errors. Avoiding spaces prevents issues in scripts, build tools, and asset references, and using clear prefixes or suffixes helps identify the asset type at a glance. Including version identifiers tells you which iteration is current, simplifies tracking changes, and makes it easy to revert or compare different versions. An organized folder structure groups related assets together, making navigation, searching, and applying changes with version control much smoother. Choices that skip a naming convention lead to confusion and harder collaboration, while allowing spaces or relying on folders alone can cause path and tooling problems. Never versioning asset names eliminates traceability and makes merging and history tracking far more difficult.