Get App

Python: Which practice avoids a common mistake with concurrent.futures?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with concurrent.futures?

  1. Do not submit unbounded work blindly without considering pool size, result ordering, failure handling, and backpressure.
  2. Ignore the concurrent.futures issue and rely on team discipline instead of clearer APIs or invariants.
  3. Silence the concurrent.futures problem by using broad catches, hidden globals, or extra shared mutable state.
  4. Prefer the version of concurrent.futures 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: A. Do not submit unbounded work blindly without considering pool size, result ordering, failure handling, and backpressure.

Do not submit unbounded work blindly without considering pool size, result ordering, failure handling, and backpressure. This is a common failure mode in real Python code and a frequent interview follow-up.

Track: Python