Concurrency · interview question
A bug appears around async def and await. What is the strongest first debugging move?
Multiple choiceEasychapter-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. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. 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?