Cloud Storage Sync and Collaboration: Selective Sync, Version History, and Why Sync Is Not Backup

Cloud storage sync clients such as OneDrive, Google Drive for desktop, and Dropbox keep a local folder and a cloud copy identical: change a file on either side and the change replicates to the other, including deletions. That replication is what makes sync convenient — and it is exactly why sync is not backup, because a mistake propagates as faithfully as a save. The features layered on top — selective sync, status icons, version history, and collaborative editing tools — are what the 220-1202 exam asks technicians to configure and troubleshoot, and what A+ Core 2 practice questions probe from every angle.

How a sync client works

After you install the client and sign in, it designates one or more local folders as synced. A background agent watches those folders and the cloud account for changes and reconciles them continuously in both directions. The client surfaces its health through status icons overlaid on files and shown on the notification-area icon: a green check means synced, spinning arrows mean sync in progress, a cloud outline means the file is online-only, and a red X means sync has failed. Modern clients also offer Files On-Demand (OneDrive’s name for it), which shows every cloud file in File Explorer but downloads content only when a file is opened — placeholders cost almost no disk space.

Two consequences follow from the mirroring model. Anything you change locally changes in the cloud, and — the part users forget — anything you delete locally is deleted from the cloud and then from every other synced device. The service’s recycle bin or trash is usually the only safety net, and it expires.

Selective sync: choosing what lives on this machine

Selective sync (OneDrive calls it “Choose folders”) lets a user pick which cloud folders replicate to a given computer while the rest remain cloud-only. It is the standard answer to a small SSD (solid-state drive) filling up with a large cloud account: on the user’s laptop, open the client’s settings, find the folder-selection screen, and uncheck the bulky folders — they stay safe in the cloud and on other machines, just not on this disk. Selective sync excludes whole folders from a device; Files On-Demand instead keeps everything visible as placeholders and streams content when needed. The exam distinguishes those two: “choose specific folders to sync locally” is selective sync, “see all files but only download on open” is Files On-Demand.

Troubleshooting a sync failure (the red X)

When a user reports that recent changes are not appearing in the cloud and the client’s icon shows a red X or error badge, work from the cheapest checks outward. First, click the icon and check the client’s own status: is the user still signed in, and is sync paused or erroring? Expired credentials — a changed password, an aged-out work or school sign-in token — are the most common cause, and the client will sit disconnected until someone reauthenticates. After sign-in status, the checklist runs: internet connectivity, sync paused (battery-saver and metered-connection settings pause sync automatically), local disk or cloud storage quota full, and finally per-file problems such as illegal characters, path length, or a file locked open. The habit the exam rewards is reading the client’s reported state before touching anything else — the icon usually names the problem.

Version history vs. Track Changes

Cloud productivity suites give you two different recovery-and-review tools, and scenario questions hinge on telling them apart.

Version history is file-level rollback. The service snapshots the document as it is edited, and any collaborator can open the version list and restore the file to an earlier point in time. When someone accidentally deletes an entire slide from a shared presentation, version history is the feature that brings back the pre-deletion state of the file — no backup software involved, because the platform kept the old versions itself.

Track Changes (Google’s equivalent mode is called “Suggesting”) is edit-level review. It records each insertion and deletion attributed to its author, displayed inline, and lets a reviewer accept or reject each individual change rather than reverting the whole document. An editor who wants to see exactly which words each collaborator added or removed, and rule on them one at a time, needs Track Changes — version history can only swap the entire file for an older one.

Aspect	Version history	Track Changes / Suggesting
Granularity	Whole file, point-in-time	Individual insertions/deletions
Attribution	Which version, by whom, when	Each edit tagged to its author
Recovery action	Restore an earlier version	Accept or reject each change
Best for	Undoing accidents, corruption, overwrites	Editorial review of collaborators’ edits

Real-time co-authoring, shared links with view/comment/edit permission levels, and in-document comments round out the collaboration feature set; a technician’s job is usually enabling the right permission level rather than emailing file copies around. Web-based suites also sidestep the cross-platform application problems described in desktop and mobile OS types, since a browser is all any device needs.

Sync is not backup

Here is the trap that costs users real data. Because a folder “goes to the cloud,” users assume it is backed up. But a sync service’s contract is make all copies identical — so when the user deletes a file locally, the client dutifully deletes the cloud copy, and every other synced device follows. One action destroyed every replica. A backup, by contrast, is an independent, point-in-time copy that a later deletion cannot reach: deleting the original leaves the backup untouched, and older backup sets preserve older states. Sync optimizes for availability of the current state everywhere; backup preserves past states somewhere the current state cannot overwrite them. Version history and the service recycle bin blur the line — they can rescue single files — but both have retention limits and neither protects against a deprovisioned account or a wiped folder tree. The professional recommendation on a service call: keep the sync client for convenience, and pair it with a genuine backup (image or file-level, on a separate destination) for protection. Mail configuration follows the same server-authoritative logic, covered in IMAP vs POP3.

How the 220-1202 exam tests this

• Setting identification: a user wants only certain folders on the local disk with the rest cloud-only, and the question asks which client setting does it — selective sync (“Choose folders”), with Files On-Demand as the tempting distractor.
• First-step triage: the OneDrive icon shows a red X and changes are not uploading; the question asks what to check FIRST — the client’s sign-in/status, before reinstalling or blaming the network.
• Concept illustration: a user deletes a synced file, it vanishes from the cloud and all devices, and the question asks what this demonstrates — that synchronization is not backup, because deletions replicate.
• Feature discrimination: restore a file to before a bad edit (version history) versus review and accept/reject each collaborator’s individual edits (Track Changes) — the stems are written so only the granularity difference separates the answers.

For how this objective fits into the broader Operating Systems domain and the rest of the exam, see the full 220-1202 study guide.

Quick reference

• Sync clients mirror a local folder and the cloud in both directions — including deletions.
• Status icons: green check synced, arrows syncing, cloud outline online-only, red X sync failed.
• Selective sync excludes chosen folders from a device; Files On-Demand keeps placeholders and downloads on open.
• Red X triage order: sign-in status and client errors first, then connectivity, paused sync, quota, then per-file issues.
• Version history restores the whole file to an earlier point in time.
• Track Changes / Suggesting shows each author’s edits and lets a reviewer accept or reject them individually.
• Deleting a synced file deletes it everywhere — sync is not backup.
• Pair sync with an independent backup destination; recycle bins and version history have retention limits.