Question
When should a Python developer choose Variables, References, and Mutability deliberately?
- Choose Variables, References, and Mutability mainly when you want to postpone validation and fix issues manually later.
- Choose Variables, References, and Mutability whenever you want the code to look more advanced, even if the design gets less clear.
- Explain this deliberately when code shares lists, dicts, or nested objects across helpers and side effects would matter.
- Choose Variables, References, and Mutability only to avoid modeling the real data shape or domain contract explicitly.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: C. Explain this deliberately when code shares lists, dicts, or nested objects across helpers and side effects would matter.
Explain this deliberately when code shares lists, dicts, or nested objects across helpers and side effects would matter. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python