TrackEX0014

Google Drive

Hard

Problem

An auditor just asked why a user who was removed from a shared folder twenty minutes ago could still open a file inside it. The investigation finds the permission check never actually touched a current source of truth. It trusted a cache with no real invalidation path. Build the metadata and authorization layer for a cloud file-storage platform: who owns each file and folder, how folders nest, who a file or folder is shared with, and what happens when two people rename or move the same item at the same time. This is the control plane, not the file-transfer data plane; assume file bytes land in a separate blob store once authorized. Design it from a blank canvas so every single read is authorized before anything is served, a concurrent rename or move never silently discards one person's edit, and a revoked share stops working within a short, bounded window instead of an indefinite one.

Required components

Click to add a component to the canvas.

Additional components

Browse by category. Click or drag a component onto the canvas.

Drag components from the library onto the canvas, then drag from a component's right handle to connect it to another.

100%

Design canvas

Sign up to start designing

Sign up free

Premium is free for 58 more days.

$0 / $2,100