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

4 questions in Layered Architecture.

Quiz

A design has four layers. The service layer contains no logic - it forwards every call from the controller to the repository. What would you change?

A layered architecture is described as outdated. When is it still the right choice, and what is its real limitation?

A team applies a strict layered architecture and finds every change touches nine files. Is layering wrong, or is the application wrong?

A team's rule is that the domain layer must not import the persistence layer. Today the rule lives in a wiki page and in code review. What changes when the same rule becomes a check that fails the build, and what does the violation count over time tell you that today's count does not?