Question
When should a Python developer choose LEGB Scope and Closures deliberately?
- Choose LEGB Scope and Closures mainly when you want to postpone validation and fix issues manually later.
- Use closures deliberately for small factories and decorators when the captured value genuinely belongs with the returned callable.
- Choose LEGB Scope and Closures whenever you want the code to look more advanced, even if the design gets less clear.
- Choose LEGB Scope and Closures 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: B. Use closures deliberately for small factories and decorators when the captured value genuinely belongs with the returned callable.
Use closures deliberately for small factories and decorators when the captured value genuinely belongs with the returned callable. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python