Get App

Java: Which practice avoids a common mistake with BlockingQueue and Producer-Consumer?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with BlockingQueue and Producer-Consumer?

  1. Do not rebuild blocking coordination manually with sleep loops when a blocking queue already expresses the intent safely.
  2. Ignore the BlockingQueue and Producer-Consumer issue and rely on team discipline instead of APIs or contracts.
  3. Silence the BlockingQueue and Producer-Consumer problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of BlockingQueue and Producer-Consumer that makes behavior less predictable as long as the code compiles.

Hint

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

Answer and rationale

Correct answer: A. Do not rebuild blocking coordination manually with sleep loops when a blocking queue already expresses the intent safely.

Do not rebuild blocking coordination manually with sleep loops when a blocking queue already expresses the intent safely. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java