Concurrency · interview question
What assumption should be made explicit when working with cancellation?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencycancellation
Answer and explanation
Correct answer
B. The expected data shape, boundary rule, or invariant that the rest of the code depends on staying true.
Why
Once assumptions are explicit, bugs are easier to detect and test cases are easier to design.
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?
- Which option describes the most likely pitfall around cancellation?
- 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?