Memory · interview question
Which judgment is strongest when choosing a data shape for long-lived objects?
Multiple choiceHardchapter-16-curatedpremiummemorylong-lived-objects
Answer and explanation
Correct answer
D. Pick the structure that matches the business meaning and the operations you need to perform repeatedly.
Why
The right shape makes the rest of the code simpler. The wrong shape forces awkward fixes everywhere else.
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?