Question
Which practice avoids a common mistake with Tree Fundamentals?
- Ignore the Tree Fundamentals issue and rely on team discipline instead of APIs or contracts.
- Silence the Tree Fundamentals problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of Tree Fundamentals that makes behavior less predictable as long as the code compiles.
- Do not mix up tree depth, height, and level terminology when explaining traversal or complexity.
Hint
Look for the option that protects correctness instead of hiding the problem.
Answer and rationale
Correct answer: D. Do not mix up tree depth, height, and level terminology when explaining traversal or complexity.
Do not mix up tree depth, height, and level terminology when explaining traversal or complexity. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java