Get App

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

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Monotonic Stack?

  1. Ignore the Monotonic Stack issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Monotonic Stack problem by using raw types, broad catches, or shared mutable state.
  3. Do not push values when the problem needs indices, because distance calculations usually depend on positions.
  4. Prefer the version of Monotonic 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: C. Do not push values when the problem needs indices, because distance calculations usually depend on positions.

Do not push values when the problem needs indices, because distance calculations usually depend on positions. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java