Concurrency · interview question
Which explanation would sound strongest in an interview when discussing semaphores, timeouts, and cancellation?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencysemaphores-timeouts-and-cancellation
Answer and explanation
Correct answer
B. Apply limits and timeouts so one slow dependency or surge does not saturate the rest of the workflow. Interviewers like answers that mention backpressure, limits, and cleanup.
Why
Interviewers usually care less about keywords than about whether you can explain why the code is shaped the way it is.
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?