Concurrency · interview question
What does a strong engineer do when reasoning through async def and await code?
Multiple choiceMediumchapter-15-curatedpremiumconcurrencyasync-def-and-await
import asyncio
async def fetch_order(order_id: str) -> dict[str, str]:
await asyncio.sleep(0.1)
return {"order_id": order_id}Answer and explanation
Correct answer
D. Narrate the data shape, the state changes, and the exact rule order step by step.
Why
Interviewers often use simple code to test whether you can reason through execution without bluffing.
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?