Memory · interview question
When is long-lived objects being used in the wrong way?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
B. When it adds cleverness or indirection without making the rule clearer, safer, or easier to test.
Why
A feature is justified by clarity and leverage, not by novelty. Focus on why the correct option matches the concept and why the distractors are weaker in this scenario.
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?