This set builds vocabulary for cloud file synchronization and sharing concepts.
0 / 5 completed
1 / 5
At standup, a dev mentions a folder that automatically mirrors its contents across every device signed into the same account whenever a file changes. What is this capability called?
Cloud file synchronization automatically mirrors a folder's contents across every device signed into the same account whenever a file is added, edited, or deleted, keeping all devices consistent without manual copying. This background syncing is the core value proposition of a cloud file storage service like Dropbox. It removes the friction of manually transferring files between a laptop, phone, and other devices.
2 / 5
During a design review, two team members edit the same file simultaneously while offline, and the sync service creates two separate copies once reconnected. What is this outcome called?
A sync conflict occurs when the same file is edited in two places without network connectivity to coordinate the changes, and rather than silently discarding one version, the sync service typically preserves both as a conflicted copy for a human to manually reconcile. This preserves data at the cost of requiring manual resolution afterward. Understanding this behavior helps a team recognize and resolve conflicted copies rather than assuming a change was lost.
3 / 5
In a code review, a dev enables a setting so certain large or infrequently used files stay in the cloud and don't consume local disk space until opened. What is this feature called?
On-demand sync keeps certain files as lightweight cloud placeholders that don't consume local disk space until actually opened, letting a user access their full cloud library without needing enough local storage to hold every file at once. This is especially useful on devices with limited storage relative to the total size of the synced library. It trades a brief download delay on first access for significant local storage savings.
4 / 5
An incident report shows a shared folder's permissions were misconfigured, giving external collaborators write access to files meant to be read-only. What practice would prevent this?
Explicitly reviewing and setting the correct sharing permissions before granting external access prevents a collaborator from having broader access, like write permission on files meant to be read-only, than actually intended. Assuming a safe default without checking is how this kind of overly permissive sharing slips through. This verification step applies to any cloud storage platform's sharing configuration, not one specific product.
5 / 5
During a PR review, a teammate asks why the team relies on cloud file sync instead of manually emailing files back and forth or copying them to a USB drive. What is the reasoning?
Manually emailing files or copying them via USB drive risks someone working from an outdated version, since there's no automatic mechanism keeping copies consistent, while synchronization keeps everyone's local copy current automatically as changes happen. This reliability advantage grows with the number of people collaborating on the same files. The tradeoff is a dependency on the sync service's availability and correct configuration.