Concurrency · interview question
Which explanation would sound strongest in an interview when discussing async def and await?
Multiple choiceEasychapter-15-curatedpremiumconcurrencyasync-def-and-await
Answer and explanation
Correct answer
D. Use async and await when the work is largely waiting on I/O and the code can be structured around cooperative suspension. Interviewers often want to hear why the model fits the workload, not only how await looks.
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 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?
- If you wrote a test around async def and await, what should the test prove first?