A folder contains files dated '3-16-2026', '10-5-2025', and '1-2-2026'. When these files are sorted alphabetically by name, what order will they appear in?
A10-5-2025, 1-2-2026, 3-16-2026 — correctly sorted oldest to newest
B1-2-2026, 10-5-2025, 3-16-2026 — sorted by leading character, not chronologically
C3-16-2026, 1-2-2026, 10-5-2025 — sorted by month
DThe sort order depends on the operating system and cannot be predicted
Alphabetical sorting is lexicographic — it compares character by character from left to right. '1' comes before '10' which comes before '3', so American-format dates produce the chaotic order: 1-2-2026, 10-5-2025, 3-16-2026. ISO format (YYYY-MM-DD) solves this by placing the most significant unit first. Two files with the same year are then compared by month, and so on — lexicographic order and chronological order coincide.
Question 2 Multiple Choice
A project folder contains: final_report.docx, final_report_v2.docx, final_report_FINAL.docx, final_report_FINAL_v2.docx, final_report_actually_final.docx. What does this naming pattern most clearly reveal about the author's practice?
AToo many collaborators were editing the file simultaneously without coordination
BThe author did not build versioning into the name from the start, so each new version required an awkward suffix
CThe project scope grew unexpectedly, requiring many revision cycles
DThe file system prevented overwriting files with the same name
This anti-pattern is the predictable outcome of starting with 'final_report.docx' — a name with no version information. Once a file is named 'final,' the next revision has nowhere natural to go. If the author had used 'report_v1.docx' or 'report_2026-03.docx' from the start, each subsequent version would fit into a legible sequence. The fix is to include versioning information before you ever need it.
Question 3 True / False
Spaces in file names are primarily a style preference with no technical consequences.
TTrue
FFalse
Answer: False
Spaces cause real technical problems: command-line tools require special escaping (a file called 'my report.txt' must be written as 'my\ report.txt' or quoted in shells), URLs encode spaces as '%20', and scripts that parse file paths break silently on unexpected spaces. This is why underscores or hyphens as word separators are a strong convention in technical contexts — it eliminates a category of hard-to-diagnose errors.
Question 4 True / False
Using ISO date format (YYYY-MM-DD) in file names means that a folder of date-stamped files will automatically sort in chronological order when sorted alphabetically.
TTrue
FFalse
Answer: True
ISO format works precisely because it places the most significant unit first: year, then month, then day. Alphabetical (lexicographic) sorting compares left-to-right, so two files with the same year are compared by month, and same-month files are compared by day. The result is that lexicographic order and chronological order are identical — which is the entire reason ISO date format is the convention for file names, log timestamps, and data exports.
Question 5 Short Answer
Why is organizing project files into folders named 'Draft,' 'Review,' and 'Final' a poor long-term strategy compared to organizing by project or topic first?
Think about your answer, then reveal below.
Model answer: Phase-based folders become unnavigable as soon as you work on more than one project at a time — every 'Draft' folder fills with unrelated files from different contexts. Organizing by project or topic keeps related files together; the version or phase can then be encoded in the file name itself (e.g., 'report_v1.docx'). Good organization reflects how you search for things, not the order in which you created them.
The failure mode is predictable: after a few months with multiple simultaneous projects, 'Draft' contains thirty unrelated files and you cannot find anything without opening each one. Project-first organization — 'ClientX/report_v1.docx' — makes both context and version visible at a glance, and it scales as the number of projects grows.