Get App

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

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

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

  1. Ignore the ArrayDeque as a Stack issue and rely on team discipline instead of APIs or contracts.
  2. Do not model stack logic with LinkedList by default when ArrayDeque communicates the intent more directly.
  3. Silence the ArrayDeque as a Stack problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of ArrayDeque as a Stack 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: B. Do not model stack logic with LinkedList by default when ArrayDeque communicates the intent more directly.

Do not model stack logic with LinkedList by default when ArrayDeque communicates the intent more directly. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java