Multi-region SaaS data sovereignty
Design the multi-region architecture for a B2B HR/payroll SaaS serving enterprise tenants in the US, EU, and India. EU tenant data must never leave the EU and Indian tenant data must stay in India (data-sovereignty law), yet the company wants a single global application and the ability to recover a region within an hour if it's lost. How do you place tenant data, route requests, and do disaster recovery without violating sovereignty?
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.
Clarify5:30 left
Estimate5:30 planned
Design16:30 planned
Deep dive13:30 planned
Failure9: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.