Get App

Java: Which practice avoids a common mistake with Queue Fundamentals?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Queue Fundamentals?

  1. Ignore the Queue Fundamentals issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Queue Fundamentals problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Queue Fundamentals that makes behavior less predictable as long as the code compiles.
  4. Do not call a structure a queue if the removal policy is actually priority-based or stack-like.

Hint

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

Answer and rationale

Correct answer: D. Do not call a structure a queue if the removal policy is actually priority-based or stack-like.

Do not call a structure a queue if the removal policy is actually priority-based or stack-like. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java