Question
When should a Python developer choose Reference Counting and Garbage Collection deliberately?
- Choose Reference Counting and Garbage Collection mainly when you want to postpone validation and fix issues manually later.
- Choose Reference Counting and Garbage Collection whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Reference Counting and Garbage Collection only to avoid modeling the real data shape or domain contract explicitly.
- Use this knowledge when debugging memory growth, object lifetime, or why resources should still be closed explicitly instead of waiting for collection.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use this knowledge when debugging memory growth, object lifetime, or why resources should still be closed explicitly instead of waiting for collection.
Use this knowledge when debugging memory growth, object lifetime, or why resources should still be closed explicitly instead of waiting for collection. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python