Memory · interview question
Which option treats long-lived objects as an engineering policy decision instead of a syntax trick?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
D. Use it to make the operational rule explicit, observable, and maintainable under real workload conditions.
Why
Senior answers focus on ownership, reliability, and maintainability rather than only API recall.
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?
- If long-lived objects fails in production, what handling philosophy is strongest?