Question
When should a Python developer choose Comprehensions deliberately?
- Choose a comprehension when the transformation is simple enough that the data flow is still obvious in one read.
- Choose Comprehensions mainly when you want to postpone validation and fix issues manually later.
- Choose Comprehensions whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Comprehensions 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: A. Choose a comprehension when the transformation is simple enough that the data flow is still obvious in one read.
Choose a comprehension when the transformation is simple enough that the data flow is still obvious in one read. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python