Get App

Java: Which practice avoids a common mistake with Heap vs Stack?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Heap vs Stack?

  1. Ignore the Heap vs Stack issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Heap vs Stack problem by using raw types, broad catches, or shared mutable state.
  3. Do not explain every Java performance problem with only the simple stack-vs-heap story.
  4. Prefer the version of Heap vs 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 explain every Java performance problem with only the simple stack-vs-heap story.

Do not explain every Java performance problem with only the simple stack-vs-heap story. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java