Concurrency · interview question
Which boundary choice best fits async def and await in a maintainable Python system?
Multiple choiceEasychapter-15-curatedpremiumconcurrencyasync-def-and-await
Answer and explanation
Correct answer
B. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
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?