A good pattern might include date, project, content type, version, and owner.
A useful file name is consistent, descriptive, sortable, and avoids ambiguous 'final-final' versions; the exam trap is picking a name that looks helpful but breaks sorting or lacks a version marker.