Quiz

2777 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 areas2777 Architecture Fundamentals81 Distributed Systems101 Data Architecture90 Cloud Architecture87 Networking86 API & Integration Architecture87 Reliability & Resilience99 Observability92 Performance & Capacity Engineering90 Security Architecture95 Cost Architecture & FinOps92 Business Architecture93 Architecture Communication91 Enterprise Architecture100 Legacy Modernization92 AI-Era Architecture96 Software Architecture & Engineering93 Architecture Patterns84 Architecture Decision-Making91 The Architect's Meta-Skills92 Delivery & Release Engineering93 Platform Engineering & Developer Experience92 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data93 Data Governance & Semantics91 Frontend & Experience Architecture91 Edge, Mobile & IoT88 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

2777 questions.

Quiz

A recommendation platform stores petabytes of interaction events used for both ad-hoc analysis and model training, with occasional need to delete individual users' data. Which storage architecture fits, and why does the deletion requirement drive the choice?

You are asked to choose between a cloud data warehouse and a lakehouse for a new analytics platform. How do you decide?

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 CDO proposes moving to a data mesh because the central data team is a bottleneck with a nine-month backlog. How do you assess the proposal?

A large enterprise wants to move from a central data team to a decentralised model. What determines whether that succeeds, and what does it not fix?

An interviewer says "we are going federated across about 40 domains. Which governance policies do we put in the platform as code and which stay as written guidance? Talk me through how you decide, and what the code version costs us."

An organisation is considering data mesh. What problem does it actually solve, what does it require, and when is a central platform team the better answer?

What must exist before decentralising data ownership makes things better rather than worse?

A 6 TB order history must be backfilled into a new store before cutover. The link sustains 1 Gbps and the target ingests about 40 MB/s per writer. Roughly how long is the backfill, and which assumption decides whether it fits one weekend?