Get App

Java: Which practice avoids a common mistake with ArrayDeque as a Queue?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with ArrayDeque as a Queue?

  1. Do not treat ArrayDeque as thread-safe; concurrent producers and consumers need concurrent queue types instead.
  2. Ignore the ArrayDeque as a Queue issue and rely on team discipline instead of APIs or contracts.
  3. Silence the ArrayDeque as a Queue problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of ArrayDeque as a Queue 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 treat ArrayDeque as thread-safe; concurrent producers and consumers need concurrent queue types instead.

Do not treat ArrayDeque as thread-safe; concurrent producers and consumers need concurrent queue types instead. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java