Quiz

2667 questions of the kind that actually get asked — in interviews, in architecture review boards, and by the person who has to run the thing at 3 AM. Every answer states the trade-off rather than the slogan, and says when the obvious choice is the wrong one.

All areas2667 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture78 Reliability & Resilience88 Observability81 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture91 Legacy Modernization92 AI-Era Architecture86 Software Architecture & Engineering84 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture90 Data Platform Architecture88 Streaming & Real-Time Data93 Data Governance & Semantics81 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture90 Assurance, Audit & Model Risk88

Difficulty Any beginner intermediate advanced

60 questions in Data Architecture.

Quiz

A GDPR erasure request arrives for a customer. Where does their data actually live, and what makes this expensive to retrofit?

A consumer fintech accumulates transaction, behavioural and derived data. How should retention, archival, deletion and regulatory holds be designed so they do not conflict?

A customer exercises their right to erasure. List every place their data plausibly exists in a mature architecture and how each is handled.

A file storage platform must permanently delete a user's data on request, while maintaining backups, replicas, caches and search indexes. What makes this genuinely difficult, and how is it designed?

A finance report double-counts revenue after a new fact table is added. What is the likely modelling error?

A travel platform runs thousands of experiments simultaneously and needs its warehouse to support reliable analysis. What warehouse design decisions prevent cross-experiment contamination and infrastructure artefacts from being read as results?

A daily pipeline has been producing wrong numbers for three weeks due to a logic bug. What must be true of the architecture for the fix to be a one-day job?

A brokerage proposes event sourcing for its account ledger. What requirements would genuinely justify it, and when is conventional state plus an audit trail the safer choice?

A neobank stores every account change as an immutable fact rather than a mutable balance. Which needs justify this, how are balances materialised for fast reads, and what happens when a projection is found to be wrong?

A system is event-sourced. A customer exercises their right to erasure. The event log is immutable. How do you comply?

A team wants event sourcing for a new order service, citing audit requirements. What do you recommend?

An organisation wants event sourcing for its order platform because it is considered scalable. What business or audit requirements would actually justify it, and when is CRUD plus an audit log safer?