Get App

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

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Stack Fundamentals?

  1. Do not reach for recursion automatically when an explicit stack would make state transitions clearer or safer.
  2. Ignore the Stack Fundamentals issue and rely on team discipline instead of APIs or contracts.
  3. Silence the Stack Fundamentals problem by using raw types, broad catches, or shared mutable state.
  4. Prefer the version of Stack Fundamentals 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 reach for recursion automatically when an explicit stack would make state transitions clearer or safer.

Do not reach for recursion automatically when an explicit stack would make state transitions clearer or safer. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java