Question
Which statement about concurrent.futures is the strongest interview answer?
- concurrent.futures is mostly a naming style choice and has little effect on runtime behavior or design tradeoffs.
- concurrent.futures offers a higher-level API for thread or process pools so tasks can be submitted and collected with a common interface.
- concurrent.futures exists mainly to reduce the number of files in a Python project.
- concurrent.futures matters only for frontend scripting and not for backend or automation code.
Hint
Start with the core rule behind concurrent.futures.
Answer and rationale
Correct answer: B. concurrent.futures offers a higher-level API for thread or process pools so tasks can be submitted and collected with a common interface.
concurrent.futures offers a higher-level API for thread or process pools so tasks can be submitted and collected with a common interface. This is the base concept interviewers commonly test first.
Track: Python