Concurrency · interview question
Which move is the best default when async def and await become part of this workflow?
Multiple choiceEasychapter-15-curatedpremiumconcurrencyasync-def-and-await
Answer and explanation
Correct answer
A. Use async and await when the work is largely waiting on I/O and the code can be structured around cooperative suspension.
Why
Use async and await when the work is largely waiting on I/O and the code can be structured around cooperative suspension. That is the stronger engineering move because interviewers often want to hear why the model fits the workload, not only how await looks. Calling everything async without a workload reason creates complexity without guaranteed benefit.
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?