Question
When should a Python developer choose concurrent.futures deliberately?
- Choose concurrent.futures mainly when you want to postpone validation and fix issues manually later.
- Choose concurrent.futures whenever you want the code to look more advanced, even if the design gets less clear.
- Choose concurrent.futures only to avoid modeling the real data shape or domain contract explicitly.
- Choose concurrent.futures when you want pragmatic pool-based concurrency without hand-managing worker threads or processes.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Choose concurrent.futures when you want pragmatic pool-based concurrency without hand-managing worker threads or processes.
Choose concurrent.futures when you want pragmatic pool-based concurrency without hand-managing worker threads or processes. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python