Get App

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

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

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

  1. Do not ignore recursion depth risk in large graphs when an explicit stack may be safer in production code.
  2. Ignore the Depth-First Search issue and rely on team discipline instead of APIs or contracts.
  3. Silence the Depth-First Search problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Depth-First Search 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 ignore recursion depth risk in large graphs when an explicit stack may be safer in production code.

Do not ignore recursion depth risk in large graphs when an explicit stack may be safer in production code. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java