Question
Which practice avoids a common mistake with Balanced Search Trees?
- Ignore the Balanced Search Trees issue and rely on team discipline instead of APIs or contracts.
- Silence the Balanced Search Trees problem by using raw types, broad catches, or shared mutable state.
- Do not hand-wave balancing as self-correcting magic; the tree needs explicit invariants and restructuring rules.
- Prefer the version of Balanced Search Trees 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 hand-wave balancing as self-correcting magic; the tree needs explicit invariants and restructuring rules.
Do not hand-wave balancing as self-correcting magic; the tree needs explicit invariants and restructuring rules. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java