InterviewsVector
AdvancedPrincipalData Architecture & Consistency65 minutesPro answer

SDV-013

Place tenant data under conflicting residency and collaboration rules

Model residency as enforceable policy across primary data, derived indexes, telemetry, support access, and cross-region collaboration.

Data ResidencyMulti TenancyComplianceConsistency

Interview prompt

Problem context

An enterprise SaaS product must keep EU tenant content in selected countries, but users collaborate with external guests worldwide. Search, analytics, backups, support tools, and machine-learning features currently copy data globally. Design data placement and product semantics that can be explained to auditors and customers.

Skills being evaluated

data classificationpolicy enforcementregional data architecturecompliance trade-offs

The full reasoning guide is part of Pro

The scenario and evaluation focus above remain public. Pro unlocks the structured answer, trade-off analysis, follow-up probes, common weak answers, rubric, related reasoning, and any architecture diagram.

Sign in to continue

What the full guide covers

Clarify the decision
Establish scale assumptions
Functional and non-functional requirements
High-level architecture
Data model and flow
Consistency and transaction boundaries
Failure modes and recovery
Security and privacy
Observability and SLOs
Capacity and cost
Alternatives and trade-offs
Evolution and migration
What Staff and Principal candidates should emphasize

Related architecture decisions

Staff · 60 min

Assign write ownership in a multi-region active-active product

Design per-domain and per-entity write ownership instead of hand-waving conflicts away with “active-active,” while meeting latency and outage goals.

Staff · 55 min

Delete customer data across replicas, indexes, logs, and backups

Design a deletion state machine with lineage, tombstones, cryptographic erasure, retention exceptions, and proof across a sprawling data estate.

Senior · 55 min

Design enterprise SaaS tenant isolation as a graduated set of boundaries

Match logical, resource, data, key, and cell isolation to tenant risk and economics without claiming one database row filter solves everything.

Senior · 55 min

Migrate a multi-terabyte database without downtime or wishful dual writes

Plan snapshot, change capture, validation, cutover, rollback, and cleanup for a live database whose write rate and long tail make naïve copying unsafe.