Question
In Java, which comparison about Garbage Collection is accurate?
- There is no practical difference in behavior, performance, or API design when Garbage Collection is involved.
- Eligibility for collection depends on reachability, not merely on a variable going out of scope in source code.
- The oldest option related to Garbage Collection is always the right production choice regardless of context.
- Differences around Garbage Collection are mostly cosmetic, so correctness and maintainability do not change.
Hint
Focus on the behavior or tradeoff, not just the keyword.
Answer and rationale
Correct answer: B. Eligibility for collection depends on reachability, not merely on a variable going out of scope in source code.
Eligibility for collection depends on reachability, not merely on a variable going out of scope in source code. This is the comparison that usually separates memorization from understanding.
Track: Java