Skip to content
Sharp

Concurrency interview questions

async def and await, Cancellation, GIL Judgment, Processes For CPU Work, Semaphores, Timeouts, and Cancellation, Task Coordination

175 questions with answers and explanations · 161 flashcards

Take a free Concurrency testAll Python Interview Prep topics

Questions (page 2 of 4)

  1. What do interviewers usually hear as a strong signal when you discuss cancellation well?Multiple choiceHard
  2. Which move is the best default when cancellation becomes part of this workflow?Multiple choiceMedium
  3. Which judgment is strongest when choosing a data shape for async def and await?Multiple choiceMedium
  4. A senior interviewer asks for one tradeoff behind async def and await. What is the strongest follow-up?Multiple choiceHard
  5. A teammate submits shaky cancellation code. Which review comment is the strongest?Multiple choiceMedium
  6. What assumption should be made explicit when working with cancellation?Multiple choiceMedium
  7. Which boundary choice best fits async def and await in a maintainable Python system?Multiple choiceEasy
  8. What is the healthiest performance judgment around cancellation?Multiple choiceMedium
  9. If cancellation fails in production, what handling philosophy is strongest?Multiple choiceMedium
  10. A teammate submits shaky async def and await code. Which review comment is the strongest?Multiple choiceEasy
  11. Which option describes the most likely pitfall around async def and await?Multiple choiceEasy
  12. A senior interviewer asks for one tradeoff behind cancellation. What is the strongest follow-up?Multiple choiceHard
  13. When is async def and await being used in the wrong way?Multiple choiceMedium
  14. Which option is the safer default when shipping code around processes for cpu work?Multiple choiceHard
  15. What kind of contract clarity matters most for task coordination?Multiple choiceHard
  16. What production risk should you worry about most if task coordination is handled lazily?Multiple choiceMedium
  17. A senior interviewer asks for one tradeoff behind semaphores, timeouts, and cancellation. What is the strongest follow-up?Multiple choiceHard
  18. Which explanation would sound strongest in an interview when discussing threads for blocking i/o?Multiple choiceMedium
  19. Another engineer will maintain this code later. What choice helps the most around semaphores, timeouts, and cancellation?Multiple choiceMedium
  20. What kind of contract clarity matters most for threads for blocking i/o?Multiple choiceHard
  21. What is the clearest sign that code around threads for blocking i/o should be refactored?Multiple choiceMedium
  22. You cannot rewrite everything today. What is the best incremental improvement around threads for blocking i/o?Multiple choiceMedium
  23. A senior interviewer asks for one tradeoff behind gil judgment. What is the strongest follow-up?Multiple choiceHard
  24. Which option describes the most likely pitfall around semaphores, timeouts, and cancellation?Multiple choiceMedium
  25. When is gil judgment being used in the wrong way?Multiple choiceHard
  26. If you wrote a test around threads for blocking i/o, what should the test prove first?Multiple choiceMedium
  27. Which option describes the most likely pitfall around processes for cpu work?Multiple choiceHard
  28. Which response shows the healthiest evidence-first mindset around semaphores, timeouts, and cancellation?Multiple choiceHard
  29. What production risk should you worry about most if threads for blocking i/o is handled lazily?Multiple choiceMedium
  30. What does a strong engineer do when reasoning through gil judgment code?Multiple choiceHard
  31. What do interviewers usually hear as a strong signal when you discuss threads for blocking i/o well?Multiple choiceHard
  32. Which boundary choice best fits semaphores, timeouts, and cancellation in a maintainable Python system?Multiple choiceMedium
  33. You cannot rewrite everything today. What is the best incremental improvement around semaphores, timeouts, and cancellation?Multiple choiceMedium
  34. What assumption should be made explicit when working with gil judgment?Multiple choiceHard
  35. When is task coordination being used in the wrong way?Multiple choiceMedium
  36. What does a strong engineer do when reasoning through semaphores, timeouts, and cancellation code?Multiple choiceMedium
  37. What assumption should be made explicit when working with threads for blocking i/o?Multiple choiceMedium
  38. Which move is the best default when processes for cpu work becomes part of this workflow?Multiple choiceHard
  39. Which judgment is strongest when choosing a data shape for task coordination?Multiple choiceMedium
  40. Which option treats processes for cpu work as an engineering policy decision instead of a syntax trick?Multiple choiceHard
  41. Which response shows the healthiest evidence-first mindset around gil judgment?Multiple choiceHard
  42. What production risk should you worry about most if processes for cpu work is handled lazily?Multiple choiceHard
  43. Which naming or modeling choice is strongest for gil judgment?Multiple choiceHard
  44. Which option treats threads for blocking i/o as an engineering policy decision instead of a syntax trick?Multiple choiceHard
  45. Which naming or modeling choice is strongest for semaphores, timeouts, and cancellation?Multiple choiceMedium
  46. Which boundary choice best fits task coordination in a maintainable Python system?Multiple choiceMedium
  47. Which explanation would best help the team align on processes for cpu work?Multiple choiceHard
  48. If processes for cpu work fails in production, what handling philosophy is strongest?Multiple choiceHard
  49. A teammate submits shaky processes for cpu work code. Which review comment is the strongest?Multiple choiceHard
  50. When is processes for cpu work being used in the wrong way?Multiple choiceHard