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

30 questions in Legacy Modernization.

Quiz

A cutover is planned for a Sunday night. What must be prepared beyond the technical steps, and what is the most commonly missing item?

A platform must cut over a critical service. What does a cutover plan need beyond the switching steps?

What is in a cutover plan besides the steps, and what would you rehearse?

A migration is complete and the old system is still running a year later. Why does decommissioning fail, and what makes it happen?

A replaced system is still running two years after its replacement went live. Why does decommissioning fail, and what makes it happen?

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?

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?

A fourteen-year-old policy system sustains roughly 350 transactions per second at its measured peak and the business peak already consumes about 260 of them. Four new services want to call it directly. Roughly how much of that system can you sell them, and what does the number decide?

New services must interact with a legacy system that cannot handle their load or their pace of change. Which integration patterns apply?