Get App

Python: Which practice avoids a common mistake with asyncio Event Loop and Tasks?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with asyncio Event Loop and Tasks?

  1. Ignore the asyncio Event Loop and Tasks issue and rely on team discipline instead of clearer APIs or invariants.
  2. Silence the asyncio Event Loop and Tasks problem by using broad catches, hidden globals, or extra shared mutable state.
  3. Do not call blocking functions directly inside async code and expect the event loop to stay responsive.
  4. Prefer the version of asyncio Event Loop and Tasks that makes behavior less predictable as long as the code still runs.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: C. Do not call blocking functions directly inside async code and expect the event loop to stay responsive.

Do not call blocking functions directly inside async code and expect the event loop to stay responsive. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python