Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Plan_v2_2025-03-14.docx | ATeammates cannot see your copy and version history cannot track it. Save the file in the shared folder so everyone works on one file. | |
| 2Right-click > Version history | BReport_2025-03-14.docx | |
| 3Use a date in the file name so the newest file is easy to find | COpens a list of earlier versions showing who changed the file and when | |
| 4Restore an earlier version after a mistake in the shared file | DThis name is confusing and has no version number or date, so nobody knows which file is the latest. Use something like Plan_v3_2025-03-14.docx. | |
| 5final_FINAL_reallyfinal2.docx | EVersion history > Restore this version | |
| 6Saving a copy to your own laptop desktop instead of the shared folder | FA clear file name that shows the version number and the date it was saved |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
Version history — A tool in a shared folder that records who changed a file and when, so you can view earlier versions and restore one. Clear names with dates or version numbers help too, like Plan_v2_2025-03-14.Second draft: Plan-v2-2025-03-14.docxSaved on 14 March 2025
Report-2025-03-14.pdfSave the file in the shared folderFile > Version history > See all changesPick an older version, then click Restore