Quiz

2988 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 areas2988 Architecture Fundamentals91 Distributed Systems111 Data Architecture100 Cloud Architecture97 Networking96 API & Integration Architecture97 Reliability & Resilience99 Observability92 Performance & Capacity Engineering100 Security Architecture105 Cost Architecture & FinOps102 Business Architecture103 Architecture Communication102 Enterprise Architecture100 Legacy Modernization102 AI-Era Architecture106 Software Architecture & Engineering93 Architecture Patterns94 Architecture Decision-Making101 The Architect's Meta-Skills102 Delivery & Release Engineering103 Platform Engineering & Developer Experience102 Testing & Quality Architecture102 Data Platform Architecture98 Streaming & Real-Time Data103 Data Governance & Semantics91 Frontend & Experience Architecture101 Edge, Mobile & IoT98 Regulatory & Data Protection Architecture99 Assurance, Audit & Model Risk98

Difficulty Any beginner intermediate advanced

5 questions in Legacy Assessment.

Quiz

A replacement for a 16-year-old claims system passed every acceptance test and went live. Six weeks later the reinsurance return it produced was rejected by finance, and nothing in the test pack was wrong. An interviewer asks how you would have found that gap during the assessment. What do you say?

A team inherits a system nobody fully understands and is asked whether to rewrite it. What should be established before answering?

A twenty-year-old core system supports most of the business. It is on unsupported technology, three people understand it, and the last replacement attempt was abandoned after two years. Design the programme.

Before modernising, a team must assess a legacy system. What should the assessment measure, and what is usually skipped?

On Salesforce's Force.com platform, a customer's custom objects and fields are rows of metadata in shared tables rather than a schema of their own (Weissman and Bobrowski described the design at SIGMOD in 2009). What does that remove from the legacy problem, and what does it not remove?