Architecture · interview question
A teammate submits shaky layered architecture code. Which review comment is the strongest?
Multiple choiceEasychapter-18-curatedpremiumarchitecturelayered-architecture
Answer and explanation
Correct answer
C. Make the rule clearer and easier to explain. Separate API, service, and data boundaries when that separation clarifies responsibility and testing seams.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Adding layers without responsibility clarity just creates longer import chains and meetings.
Test yourself on Architecture
A free test with instant, explained results. No account needed.
More Architecture questions
- What kind of contract clarity matters most for release discipline?
- Which option describes the most likely pitfall around layered architecture?
- What is the healthiest performance judgment around layered architecture?
- Which explanation would sound strongest in an interview when discussing observability?
- A senior interviewer asks for one tradeoff behind layered architecture. What is the strongest follow-up?
- If idempotency fails in production, what handling philosophy is strongest?