Memory · interview question
If long-lived objects fails in production, what handling philosophy is strongest?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
C. Fail in a way that preserves the reason, keeps the boundary honest, and avoids hiding the real source of the problem.
Why
Reliable systems preserve context. Silent failure makes the next debugging round slower and riskier.
Test yourself on Memory
A free test with instant, explained results. No account needed.
More Memory questions
- What kind of contract clarity matters most for tracing allocations?
- Which explanation would best help the team align on long-lived objects?
- Which option is the safer default when shipping code around tracing allocations?
- A bug appears around long-lived objects. What is the strongest first debugging move?
- Which option treats tracing allocations as an engineering policy decision instead of a syntax trick?
- What production risk should you worry about most if long-lived objects is handled lazily?