Question
Which practice avoids a common mistake with Lambda, map, and filter?
- Ignore the Lambda, map, and filter issue and rely on team discipline instead of clearer APIs or invariants.
- Silence the Lambda, map, and filter problem by using broad catches, hidden globals, or extra shared mutable state.
- Prefer the version of Lambda, map, and filter that makes behavior less predictable as long as the code still runs.
- Do not force business-critical logic into nested lambdas when a named helper or comprehension would be easier to test and explain.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not force business-critical logic into nested lambdas when a named helper or comprehension would be easier to test and explain.
Do not force business-critical logic into nested lambdas when a named helper or comprehension would be easier to test and explain. This is a common failure mode in real Python code and a frequent interview follow-up.
Track: Python