Concurrency · interview question
Which option is the safer default when shipping code around threads for blocking i/o?
Multiple choiceHardchapter-15-curatedpremiumconcurrencythreads-for-blocking-i-o
from concurrent.futures import ThreadPoolExecutor
with ThreadPoolExecutor(max_workers=8) as pool:
futures = [pool.submit(call_legacy_system, order_id) for order_id in order_ids]Answer and explanation
Correct answer
D. Choose the simpler shape that keeps the rule obvious, validated, and easy to observe in logs or tests.
Why
The safest default is usually the one that lowers ambiguity and makes errors easier to diagnose.
Test yourself on Concurrency
A free test with instant, explained results. No account needed.
More Concurrency questions
- What kind of contract clarity matters most for task coordination?
- What production risk should you worry about most if task coordination is handled lazily?
- A senior interviewer asks for one tradeoff behind semaphores, timeouts, and cancellation. What is the strongest…
- Which explanation would sound strongest in an interview when discussing threads for blocking i/o?
- Another engineer will maintain this code later. What choice helps the most around semaphores, timeouts, and…
- What kind of contract clarity matters most for threads for blocking i/o?