Question
In Java, which comparison about Balanced Search Trees is accurate?
- They cost more implementation complexity than a plain BST, but they protect search, insert, and delete performance from skewed input.
- There is no practical difference in behavior, performance, or API design when Balanced Search Trees is involved.
- The oldest option related to Balanced Search Trees is always the right production choice regardless of context.
- Differences around Balanced Search Trees 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: A. They cost more implementation complexity than a plain BST, but they protect search, insert, and delete performance from skewed input.
They cost more implementation complexity than a plain BST, but they protect search, insert, and delete performance from skewed input. This is the comparison that usually separates memorization from understanding.
Track: Java