Question
When should a Java developer choose Monotonic Stack deliberately?
- Choose Monotonic Stack mainly when you want to postpone validation and fix problems manually later.
- Use a monotonic stack for stock span, histogram area, daily temperatures, and nearest-greater-element interview problems.
- Choose Monotonic Stack whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Monotonic Stack only to avoid modeling domain rules explicitly in Java code.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: B. Use a monotonic stack for stock span, histogram area, daily temperatures, and nearest-greater-element interview problems.
Use a monotonic stack for stock span, histogram area, daily temperatures, and nearest-greater-element interview problems. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java