Architecture · interview question
Another engineer will maintain this code later. What choice helps the most around caching?
Multiple choiceMediumchapter-18-curatedpremiumarchitecturecaching
Answer and explanation
Correct answer
A. Make the rule obvious in names, flow, and boundaries so the next reader does not have to reverse-engineer your intent.
Why
Maintainability comes from explicit intent. Candidates sound more senior when they mention invalidation and freshness openly.
Test yourself on Architecture
A free test with instant, explained results. No account needed.
More Architecture questions
- Which explanation would best help the team align on caching?
- A senior interviewer asks for one tradeoff behind environment-based deployment. What is the strongest follow-up?
- A teammate submits shaky idempotency code. Which review comment is the strongest?
- Which option is the safer default when shipping code around container and process shape?
- Which move is the best default when idempotency becomes part of this workflow?
- Which explanation would best help the team align on container and process shape?