Get App

Java: Which practice avoids a common mistake with Breadth-First Search?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Breadth-First Search?

  1. Ignore the Breadth-First Search issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Breadth-First Search problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Breadth-First Search that makes behavior less predictable as long as the code compiles.
  4. Do not delay marking nodes as visited until much later, because duplicate enqueues can waste time and memory.

Hint

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

Answer and rationale

Correct answer: D. Do not delay marking nodes as visited until much later, because duplicate enqueues can waste time and memory.

Do not delay marking nodes as visited until much later, because duplicate enqueues can waste time and memory. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java