Question
Which statement about Threading, asyncio, and multiprocessing is the strongest interview answer?
- Threading, asyncio, and multiprocessing is mostly a naming style choice and has little effect on runtime behavior or design tradeoffs.
- Threading, asyncio, and multiprocessing exists mainly to reduce the number of files in a Python project.
- Threading, asyncio, and multiprocessing matters only for frontend scripting and not for backend or automation code.
- Python offers multiple concurrency models, and the right choice depends on whether the workload is I/O-bound, CPU-bound, or structured around cooperative async tasks.
Hint
Start with the core rule behind Threading, asyncio, and multiprocessing.
Answer and rationale
Correct answer: D. Python offers multiple concurrency models, and the right choice depends on whether the workload is I/O-bound, CPU-bound, or structured around cooperative async tasks.
Python offers multiple concurrency models, and the right choice depends on whether the workload is I/O-bound, CPU-bound, or structured around cooperative async tasks. This is the base concept interviewers commonly test first.
Track: Python