WORM compliance object store
Design a WORM (write-once-read-many) compliance object store for regulated records (financial/legal): once written, an object must be immutable and undeletable until its retention period expires — provably, even against a privileged administrator or the storage vendor — with optional indefinite legal holds. Records range from KB documents to GB archives, durability must be eleven-nines, and auditors require tamper-evident proof. How do you enforce immutability and retention you can't bypass?
What a strong answer looks like
Clarify scale and constraints first. Propose a clean component breakdown, then go deep on the hard parts (data model, bottlenecks, consistency, failure modes) and name the trade-offs you are making.
Clarify4:30 left
Estimate4:30 planned
Design13:30 planned
Deep dive10:30 planned
Failure7:00 planned
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.