Get App

Java: Which practice avoids a common mistake with Garbage Collection?

Difficulty:

Medium

Questions:

1

Time Limit:

2 minutes

Passing Score:

100%

Question

Which practice avoids a common mistake with Garbage Collection?

  1. Ignore the Garbage Collection issue and rely on team discipline instead of APIs or contracts.
  2. Silence the Garbage Collection problem by using raw types, broad catches, or shared mutable state.
  3. Prefer the version of Garbage Collection that makes behavior less predictable as long as the code compiles.
  4. Do not rely on GC timing for correctness, file cleanup, or any business-visible operation ordering.

Hint

Look for the option that protects correctness instead of hiding the problem.

Answer and rationale

Correct answer: D. Do not rely on GC timing for correctness, file cleanup, or any business-visible operation ordering.

Do not rely on GC timing for correctness, file cleanup, or any business-visible operation ordering. This is a common failure mode in real Java code and a frequent interview follow-up.

Track: Java