Question
When should a Python developer choose Threading, asyncio, and multiprocessing deliberately?
- Choose Threading, asyncio, and multiprocessing mainly when you want to postpone validation and fix issues manually later.
- Choose the model deliberately from the workload and operational constraints instead of starting from whichever API looks most advanced.
- Choose Threading, asyncio, and multiprocessing whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Threading, asyncio, and multiprocessing 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. Choose the model deliberately from the workload and operational constraints instead of starting from whichever API looks most advanced.
Choose the model deliberately from the workload and operational constraints instead of starting from whichever API looks most advanced. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Python