Concurrency · interview question
Which move is the best default when semaphores, timeouts, and cancellation becomes part of this workflow?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencysemaphores-timeouts-and-cancellation
Answer and explanation
Correct answer
C. Apply limits and timeouts so one slow dependency or surge does not saturate the rest of the workflow.
Why
Apply limits and timeouts so one slow dependency or surge does not saturate the rest of the workflow. That is the stronger engineering move because interviewers like answers that mention backpressure, limits, and cleanup. Unlimited concurrency often looks impressive in a demo and dangerous in production.
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?