Architecture · interview question
What is the clearest sign that code around observability should be refactored?
Multiple choiceHardchapter-18-curatedpremiumarchitectureobservability
Answer and explanation
Correct answer
B. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Expose enough telemetry that you can answer whether the system is healthy without remote guesswork.
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?