Question
Which practice avoids a common mistake with String Immutability?
- Do not use == to compare string content; use equals when the text value matters.
- Ignore the String Immutability issue and rely on team discipline instead of APIs or contracts.
- Silence the String Immutability problem by using raw types, broad catches, or shared mutable state.
- Prefer the version of String Immutability 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: A. Do not use == to compare string content; use equals when the text value matters.
Do not use == to compare string content; use equals when the text value matters. This is a common failure mode in real Java code and a frequent interview follow-up.
Track: Java