Concurrency · interview question
Which option describes the most likely pitfall around cancellation?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencycancellation
Answer and explanation
Correct answer
D. Ignoring cancellation leaves stray work running after the caller has already moved on.
Why
Ignoring cancellation leaves stray work running after the caller has already moved on. Calling out that risk matters because this is a good interview topic because it reveals whether you think about lifecycle, not only happy-path throughput.
Test yourself on Concurrency
A free test with instant, explained results. No account needed.
More Concurrency questions
- If you wrote a test around cancellation, what should the test prove first?
- What production risk should you worry about most if cancellation is handled lazily?
- Which option treats cancellation as an engineering policy decision instead of a syntax trick?
- What does a strong engineer do when reasoning through cancellation code?
- You cannot rewrite everything today. What is the best incremental improvement around async def and await?
- If you wrote a test around async def and await, what should the test prove first?