Question
When should a Java developer choose Immutable Class Design deliberately?
- Choose Immutable Class Design mainly when you want to postpone validation and fix problems manually later.
- Choose Immutable Class Design whenever you want the code to look more advanced, even if the design gets less clear.
- Choose Immutable Class Design only to avoid modeling domain rules explicitly in Java code.
- Use immutable value objects for money, identifiers, configuration, and messages shared across layers or threads.
Hint
Think about the production scenario where the choice genuinely improves the code.
Answer and rationale
Correct answer: D. Use immutable value objects for money, identifiers, configuration, and messages shared across layers or threads.
Use immutable value objects for money, identifiers, configuration, and messages shared across layers or threads. Interviewers often ask this to see whether you can connect the concept to real design decisions.
Track: Java