Question
When should a Java developer choose String Immutability deliberately?
- Choose String Immutability mainly when you want to postpone validation and fix problems manually later.
- Choose String Immutability whenever you want the code to look more advanced, even if the design gets less clear.
- Choose String Immutability only to avoid modeling domain rules explicitly in Java code.
- Use immutable strings for identifiers, keys, messages, and values that move across API boundaries.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use immutable strings for identifiers, keys, messages, and values that move across API boundaries.
Use immutable strings for identifiers, keys, messages, and values that move across API boundaries. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java