Get App

Java: Which practice avoids a common mistake with ConcurrentLinkedQueue?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with ConcurrentLinkedQueue?

  1. Ignore the ConcurrentLinkedQueue issue and rely on team discipline instead of APIs or contracts.
  2. Silence the ConcurrentLinkedQueue problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of ConcurrentLinkedQueue that makes behavior less predictable as long as the code compiles.
  4. Do not assume a concurrent queue provides backpressure, capacity limits, or blocking semantics by default.

Hint

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

Answer and rationale

Correct answer: D. Do not assume a concurrent queue provides backpressure, capacity limits, or blocking semantics by default.

Do not assume a concurrent queue provides backpressure, capacity limits, or blocking semantics by default. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java